Bug#775578: systemd kills spamassassin on system start

[Michael Biebl]

Control: tags -1 + moreinfo

On Sat, 17 Jan 2015 09:08:32 -0800 James Bottomley
<James.Bottomley at HansenPartnership.com> wrote:
> Package: systemd
> Version: 215-8
> Severity: normal
> 
> Almost every time the system reboots, spamassassin fails to start.  The systemd logs for this are:
> 
> # systemctl status -l spamassassin.service
> ● spamassassin.service - Perl-based spam filter using text analysis
>    Loaded: loaded (/lib/systemd/system/spamassassin.service; enabled)
>    Active: failed (Result: timeout) since Sat 2015-01-17 08:49:04 PST; 3min 45s ago
>   Process: 528 ExecStart=/usr/sbin/spamd -d --pidfile=/var/run/spamassassin.pid $OPTIONS (code=killed, signal=TERM)
> 
> Jan 17 08:48:10 bedivere spamd[528]: logger: removing stderr method
> Jan 17 08:49:04 bedivere systemd[1]: spamassassin.service start operation timed out. Terminating.
> Jan 17 08:49:04 bedivere systemd[1]: Failed to start Perl-based spam filter using text analysis.
> Jan 17 08:49:04 bedivere systemd[1]: Unit spamassassin.service entered failed state.
> Jan 17 08:49:04 bedivere spamd[748]: spamd: server killed by SIGTERM, shutting down
> Jan 17 08:49:04 bedivere spamd[748]: spamd: cannot unlink /var/run/spamassassin.pid: No such file or directory
> 
> This server is still x86 and a big internet system, so it has lots of
> intensive processes on start, like fail2ban , clamd and apache.  It
> looks like because of this, systemd gives spamassassin a few seconds
> (there's no log of how long; the logger message is from the pre-reboot
> os) to start and it takes longer.
> 
> As far as I can tell, this value doesn't seem to be configurable or
> even package specific.  It looks remarkably silly for the init system
> to impose an absolute timeout on service start, particularly when it
> doesn't take into account the characteristics of the machine or ask
> the package how long it might reasonably take.
> 
> So far, it's only spamassassin, so it's annoying but not serious to
> have to log in and restart it after every reboot.  However, if systemd
> did this to a necessary service, it would become a serious bug

Can you provide instructions how this issue can be reproduced?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20160211/f8363957/attachment.sig>