On Tue, Nov 18, 2014 at 07:38:38PM +0100, Francois Mescam wrote:
> # 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.

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")

Note that this does suggest a possible bug elsewhere, though. Spamd
should not start on new installations; instead, you should need to
enable it explicitly. In the sysvinit days, this was accomplished by
editing /etc/default/spamassassin, but with systemd it should involve
removing a mask that should be in place on fresh installations. This
mask is either missing or not created initially. I've already posted to
the pkg-systemd-maint list, and will be filing a bug soon...

noah


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to