Thanks John for the commands. Here the results
michael.heuberger@binarykitchen /v/log ❯❯❯ sudo time
/etc/init.d/spamassassin start ⏎
Starting spamassassin (via systemctl): spamassassin.service.
0.00user 0.00system 0:05.69elapsed 0%CPU (0avgtext+0avgdata
4904maxresident)k
0inputs+0outputs (0major+1844minor)pagefaults 0swaps
Hope this helps investigating my problem?
On 6/12/16 14:42, John Hardin wrote:
On Tue, 6 Dec 2016, Michael Heuberger wrote:
Thanks John
What commands would you use for shutting down SA properly and to
time-measure its restart procedure?
Hrm. Based on the start/stop commands in what you pasted earlier:
/etc/init.d/spamassassin stop
time /etc/init.d/spamassassin start
- Michael
On 6/12/16 11:15, John Hardin wrote:
On Tue, 6 Dec 2016, Michael Heuberger wrote:
> Anyone?
If you shut down SA and run the /etc/init.d/spamassassin script to
restart
it, how long does that take to complete?
Is there something like a rules recompile built into that?
> 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
--
Binary Kitchen
Michael Heuberger
1/33 Parrish Road
Sandringham
Auckland 1025
(New Zealand)
Mobile (text only) ... +64 21 261 89 81
Email ................ mich...@binarykitchen.com
Website .............. http://www.binarykitchen.com
--
Binary Kitchen
Michael Heuberger
1/33 Parrish Road
Sandringham
Auckland 1025
(New Zealand)
Mobile (text only) ... +64 21 261 89 81
Email ................ mich...@binarykitchen.com
Website .............. http://www.binarykitchen.com
