On Thu, Jun 11, 2015 at 11:40:48AM +0200, Marko von Oppen wrote:
> root@host:~# /etc/init.d/spamassassin restart
> Restarting SpamAssassin Mail Filter Daemon: No /usr/sbin/spamd found running;
> none killed.
> server socket setup failed, retry 1: spamd: could not create IO::Socket::IP
> socket
Package: spamassassin
Version: 3.4.1-4
Followup-For: Bug #788429
And BTW, for sake of completeness: on sid the restart argument to the
init script works fine without any issues:
"
root@qmitoshiba:~# /etc/init.d/spamassassin restart
[ ok ] Restarting spamassassin (via systemctl):
Package: spamassassin
Version: 3.4.1-4
Followup-For: Bug #788429
> So the 'start-stop-daemon --stop' calls in /etc/init.d/spamassassin are not
> able to identify the running spamd processes.
Note that this bug does not apply, since systemd we normally restart services
via 'systemctl restart '.
Package: spamassassin
Version: 3.4.0-6
Severity: important
Dear Maintainer,
the problem is from the same group of problems like #751772 and #741351
root@host:~# /etc/init.d/spamassassin restart
Restarting SpamAssassin Mail Filter Daemon: No /usr/sbin/spamd found running;
none killed.
server
4 matches
Mail list logo