On Tue, 6 Dec 2016, Michael Heuberger wrote:
Anyone?
On 23/11/16 16:11, Michael Heuberger wrote:
Hello folks
New here :)
I'm running Spamassassin v3.4.1 here on an headless Ubuntu 16.10 server
together with Monit (and Postfix of course). Each time server restarts,
Monit says first that the spamd process is not running (no PID) but in
three minutes later it says the opposite, that it is back up running.
There is the /etc/init.d/spamassassin file that boots Spamassassin on
start. But somehow it does not seem to get executed asap but 3 mins later.
No idea why.
The PID under /var/run/spamassassin.pid is owned by root and is monitored
under Monit with these configs:
# (hidden) @ (hidden) in /etc/monit/conf.d [14:00:04] C:1
$ cat spamassassin
check process spamd with pidfile /var/run/spamassassin.pid
group mail
start program = "/etc/init.d/spamassassin start" with timeout 180
seconds
stop program = "/etc/init.d/spamassassin stop"
if 5 restarts within 5 cycles then timeout
if cpu usage > 79% for 5 cycles then alert
if mem usage > 79% for 5 cycles then alert
depends on spamd_bin
depends on spamd_rc
check file spamd_rc with path /etc/init.d/spamassassin
group mail
if failed checksum then unmonitor
if failed permission 755 then unmonitor
if failed uid root then unmonitor
if failed gid root then unmonitor
check file spamd_bin with path /usr/sbin/spamd
group mail
if failed checksum then unmonitor
if failed permission 755 then unmonitor
if failed uid root then unmonitor
if failed gid root then unmonitor
Not sure what the problem is here. Could be one of these:
- a bug in /etc/init.d/spamassassin?
- a bad config in the above monit config
- something in postfix or another lib blocking spamassassin
No idea how to investigate. And there is no spamassassin log showing how it
starts up.
Any clues welcome
Cheers
Michael
Could it be some kind if interaction with other system services startup?
(in particular this feels like a network timeout issue).
One of the things SA does during its startup process is check to see if
DNS/network stuff is available.
If the system hasn't yet brought up the network stack when SA starts, it may
hang waiting for the network to stabilize.
On a running system, if you stop/restart SA do you see the same delay or is
it only on a cold start of the system?
Is it possible to configure a SA starup dependency on the network being up?
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
