Your message dated Sat, 22 Nov 2014 16:24:14 -0500 with message-id <20141122212414.gb3...@morgul.net> and subject line Re: Bug#770084: spamassassin: Spamassassin not installable has caused the Debian Bug report #770084, regarding spamassassin: Spamassassin not installable to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 770084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: spamassassin Version: 3.4.0-3 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Find hereafter what I obtained when I try to install spamassassin # aptitude install spamassassin # Les NOUVEAUX paquets suivants vont être installés : # libnetaddr-ip-perl{a} spamassassin # Les paquets suivants sont RECOMMANDÉS mais ne seront pas installés : # libmail-spf-perl sa-compile spamc # 0 paquets mis à jour, 2 nouvellement installés, 0 à enlever et 0 non mis à jour. # Il est nécessaire de télécharger 1 212 ko d'archives. Après dépaquetage, 4 036 ko seront utilisés. # Voulez-vous continuer ? [Y/n/?] # Prendre : 1 http://ftp.fr.debian.org/debian/ testing/main libnetaddr-ip-perl i386 4.075+dfsg-1+b1 [108 kB] # Prendre : 2 http://ftp.fr.debian.org/debian/ testing/main spamassassin all 3.4.0-3 [1 105 kB] # 1 212 ko téléchargés en 1s (1 068 ko/s) # Récupération des rapports de bogue… Fait # Analyse des informations Trouvé/Corrigé… Fait # Sélection du paquet libnetaddr-ip-perl précédemment désélectionné. # (Lecture de la base de données... 363515 fichiers et répertoires déjà installés.) # Préparation du dépaquetage de .../libnetaddr-ip-perl_4.075+dfsg-1+b1_i386.deb ... # Dépaquetage de libnetaddr-ip-perl (4.075+dfsg-1+b1) ... # Sélection du paquet spamassassin précédemment désélectionné. # Préparation du dépaquetage de .../spamassassin_3.4.0-3_all.deb ... # Dépaquetage de spamassassin (3.4.0-3) ... # Traitement des actions différées (« triggers ») pour man-db (2.7.0.2-3) ... # Paramétrage de libnetaddr-ip-perl (4.075+dfsg-1+b1) ... # Paramétrage de spamassassin (3.4.0-3) ... # # Fichier de configuration « /etc/default/spamassassin » # ==> Fichier du système créé par vous ou par un script. # ==> Fichier également présent dans le paquet fourni par le responsable du paquet. # Que voulez-vous faire ? Vos options sont les suivantes : # Y ou I : installer la version du responsable du paquet # N ou O : garder votre version actuellement installée # D : afficher les différences entre les versions # Z : suspendre ce processus pour examiner la situation # L'action par défaut garde votre version actuelle. # *** spamassassin (Y/I/N/O/D/Z) [défaut=N] ? Y # Installation de la nouvelle version du fichier de configuration /etc/default/spamassassin ... # Job for spamassassin.service failed. See 'systemctl status spamassassin.service' and 'journalctl -xn' for details. # invoke-rc.d: initscript spamassassin, action "start" failed. # dpkg: erreur de traitement du paquet spamassassin (--configure) : # le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 # Des erreurs ont été rencontrées pendant l'exécution : # spamassassin # [ Rootkit Hunter version 1.4.2 ] File updated: searched for 176 files, found 150 E: Sub-process /usr/bin/dpkg returned an error code (1) Failed to perform requested operation on package. Trying to recover: Paramétrage de spamassassin (3.4.0-3) ... Job for spamassassin.service failed. See 'systemctl status spamassassin.service' and 'journalctl -xn' for details. invoke-rc.d: initscript spamassassin, action "start" failed. dpkg: erreur de traitement du paquet spamassassin (--configure) : le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 Des erreurs ont été rencontrées pendant l'exécution : spamassassin # systemctl status spamassassin.service # ● spamassassin.service - Perl-based spam filter using text analysis # Loaded: loaded (/lib/systemd/system/spamassassin.service; disabled) # Active: failed (Result: exit-code) since mar. 2014-11-18 19:22:39 CET; 16s ago # Process: 20794 ExecStart=/usr/sbin/spamd -d --pidfile=/var/run/spamassassin.pid $OPTIONS (code=exited, status=98) # # nov. 18 19:22:33 eiffel4 spamd[20794]: server socket setup failed, retry 4: spamd: could not create IO::Soc…tilisée # nov. 18 19:22:34 eiffel4 spamd[20794]: server socket setup failed, retry 5: spamd: could not create IO::Soc…tilisée # nov. 18 19:22:35 eiffel4 spamd[20794]: server socket setup failed, retry 6: spamd: could not create IO::Soc…tilisée # nov. 18 19:22:36 eiffel4 spamd[20794]: server socket setup failed, retry 7: spamd: could not create IO::Soc…tilisée # nov. 18 19:22:37 eiffel4 spamd[20794]: server socket setup failed, retry 8: spamd: could not create IO::Soc…tilisée # nov. 18 19:22:38 eiffel4 spamd[20794]: server socket setup failed, retry 9: spamd: could not create IO::Soc…tilisée # nov. 18 19:22:39 eiffel4 spamd[20794]: spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783: Ad…tilisée # nov. 18 19:22:39 eiffel4 systemd[1]: spamassassin.service: control process exited, code=exited status=98 # nov. 18 19:22:39 eiffel4 systemd[1]: Failed to start Perl-based spam filter using text analysis. # nov. 18 19:22:39 eiffel4 systemd[1]: Unit spamassassin.service entered failed state. # Hint: Some lines were ellipsized, use -l to show in full. # # journalctl -xn # -- Logs begin at ven. 2014-11-14 22:29:29 CET, end at mar. 2014-11-18 19:22:39 CET. -- # nov. 18 19:22:33 eiffel4 spamd[20794]: server socket setup failed, retry 4: spamd: could not create IO::Socket::IP # nov. 18 19:22:34 eiffel4 spamd[20794]: server socket setup failed, retry 5: spamd: could not create IO::Socket::IP # nov. 18 19:22:35 eiffel4 spamd[20794]: server socket setup failed, retry 6: spamd: could not create IO::Socket::IP # nov. 18 19:22:36 eiffel4 spamd[20794]: server socket setup failed, retry 7: spamd: could not create IO::Socket::IP # nov. 18 19:22:37 eiffel4 spamd[20794]: server socket setup failed, retry 8: spamd: could not create IO::Socket::IP # nov. 18 19:22:38 eiffel4 spamd[20794]: server socket setup failed, retry 9: spamd: could not create IO::Socket::IP # nov. 18 19:22:39 eiffel4 spamd[20794]: spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783: Adresse dé # nov. 18 19:22:39 eiffel4 systemd[1]: spamassassin.service: control process exited, code=exited status=98 # nov. 18 19:22:39 eiffel4 systemd[1]: Failed to start Perl-based spam filter using text analysis. # -- Subject: L'unité (unit) spamassassin.service a échoué # -- Defined-By: systemd # -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel # -- # -- L'unité (unit) spamassassin.service a échoué, avec le résultat failed. # nov. 18 19:22:39 eiffel4 systemd[1]: Unit spamassassin.service entered failed state. # I use systemd on yhe system where I observe the bug. On another system also under jessie but not with systemd I do not observe the bug. Best Regards François -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages spamassassin depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.21 pn libarchive-tar-perl <none> ii libhtml-parser-perl 3.71-1+b3 ii libnet-dns-perl 0.81-1 ii libnetaddr-ip-perl 4.075+dfsg-1+b1 ii libsocket6-perl 0.25-1+b1 ii libsys-hostname-long-perl 1.4-3 ii libwww-perl 6.08-1 ii perl 5.20.1-2 ii perl-modules [libio-zlib-perl] 5.20.1-2 Versions of packages spamassassin recommends: ii gnupg 1.4.18-4 ii libio-socket-inet6-perl 2.72-1 pn libmail-spf-perl <none> ii perl [libsys-syslog-perl] 5.20.1-2 pn sa-compile <none> pn spamc <none> Versions of packages spamassassin suggests: ii libdbi-perl 1.631-3+b1 ii libio-socket-ssl-perl 2.002-2 pn libmail-dkim-perl <none> ii perl [libcompress-zlib-perl] 5.20.1-2 pn pyzor <none> pn razor <none> -- no debconf information
--- End Message ---
--- Begin Message ---On Tue, Nov 18, 2014 at 10:36:23PM +0100, Francois Mescam wrote: > > On Tue, Nov 18, 2014 at 07:38:38PM +0100, Francois Mescam wrote: > > I cannot reproduce this. Is your lo interface up, and is 127.0.0.1 > > assigned to it? (please send me the output of "/sbin/ip addr") Is > > something else maybe listening on port 783? (please send me the output > > of "sudo ss -tnlp") > > > # /sbin/ip addr > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN > group default > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever You don't have an ipv6 address on lo. How did this happen? A standard jessie install will have ::1/128 on lo, and that's the address that spamd will listen on by default. I've been able to reproduce spamd's failure to start by executing the following on a fresh jessie install: $ ip addr del ::1/128 dev lo $ apt-get install spamassassin Since ::1/128 is expected to be configured on lo, I am resolving this as not a bug. noah
--- End Message ---
