Bug#774380: spamassassin: sa-update cronjob complains when spamd is disabled

2015-09-20 Thread Samuel Wolf
Same problem here:
/etc/cron.daily/spamassassin:
Job for spamassassin.service failed. See 'systemctl status
spamassassin.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript spamassassin, action "reload" failed.

Jessie with systemd.


Bug#774380: spamassassin: sa-update cronjob complains when spamd is disabled

2015-05-17 Thread Richard van den Berg

The patch by Bernhard seems to work fine. This was bothering me since upgrading 
to jessie. Thanks!

Richard


Bug#774380: spamassassin: sa-update cronjob complains when spamd is disabled

2015-05-11 Thread Bernhard Schmidt
Source: spamassassin
Followup-For: Bug #774380

Hi,

 I guess we should simply check if spamd is running before trying to 
 reload it? Is it ok to use pidof?

How about using the status command of the initscript? Patch 
attached ...

It still has inconsistent behaviour because the sysv initscript 
checks ENABLED, but that's another issue.

Bernhard
--- a/debian/spamassassin.cron.daily	2015-05-11 10:38:11.415485334 +0200
+++ b/debian/spamassassin.cron.daily	2015-05-11 10:43:32.733327917 +0200
@@ -49,9 +49,9 @@
 reload() {
 # Reload
 if which invoke-rc.d /dev/null 21; then
-invoke-rc.d spamassassin reload  /dev/null
+invoke-rc.d --quiet spamassassin status  /dev/null  invoke-rc.d spamassassin reload  /dev/null
 else
-/etc/init.d/spamassassin reload  /dev/null
+/etc/init.d/spamassassin status  /dev/null  /etc/init.d/spamassassin reload  /dev/null
 fi
 if [ -d /etc/spamassassin/sa-update-hooks.d ]; then
 run-parts --lsbsysinit /etc/spamassassin/sa-update-hooks.d


Bug#774380: spamassassin: sa-update cronjob complains when spamd is disabled

2015-01-01 Thread Eric Dorland
Package: spamassassin
Version: 3.4.0-5
Severity: normal

Dear Maintainer,

I'm using amavis rather than spamd, so I'd like to update the rules but
don't need to run spamd, so I have ENABLED=0 and CRON=1 in
/etc/default/spamassassin. When the cronjob runs it spews an error like this:

/etc/cron.daily/spamassassin:
Job for spamassassin.service failed. See 'systemctl status 
spamassassin.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript spamassassin, action reload failed.

Presumably this is a difference between sysvinit and systemd, where systemd
complains on reload if the service is running but the sysvinit script doesn't.

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages spamassassin depends on:
ii  adduser 3.113+nmu3
ii  init-system-helpers 1.22
pn  libarchive-tar-perl none
ii  libhtml-parser-perl 3.71-1+b3
ii  libnet-dns-perl 0.81-2
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  perl5.20.1-4
ii  perl-modules [libio-zlib-perl]  5.20.1-4

Versions of packages spamassassin recommends:
ii  gnupg  1.4.18-6
ii  libio-socket-inet6-perl2.72-1
ii  libmail-spf-perl   2.9.0-3
ii  perl [libsys-syslog-perl]  5.20.1-4
ii  sa-compile 3.4.0-5
ii  spamc  3.4.0-5

Versions of packages spamassassin suggests:
pn  libdbi-perl   none
ii  libio-socket-ssl-perl 2.002-2
ii  libmail-dkim-perl 0.40-1
ii  perl [libcompress-zlib-perl]  5.20.1-4
ii  pyzor 1:0.5.0-2
ii  razor 1:2.85-4.1+b1

-- Configuration Files:
/etc/default/spamassassin changed [not included]
/etc/spamassassin/local.cf changed [not included]

-- no debconf information


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