Discussion:
Amavis keeps re-initialising
(too old to reply)
Julian Pilfold-Bagwell
2016-03-30 14:21:17 UTC
Permalink
Hi All,

I have amavisd-new, clamav and spamassassin running alongside postfix
and cyrus and I have a situation where restarting amavisd using
systemctl doesn't exit you to the command prompt, it just waits for ages
before failing and prints the following:



Job for amavisd.service failed because a timeout was exceeded. See
"systemctl status amavisd.service" and "journalctl -xe" for details.




systemctl status amavisd.service provides:



amavisd.service - Amavisd-new is an interface between MTA and content
checkers.
Loaded: loaded (/usr/lib/systemd/system/amavisd.service; enabled;
vendor preset: disabled)
Active: activating (start) since Wed 2016-03-30 15:09:11 BST; 42s ago
Docs: http://www.ijs.si/software/amavisd/#doc
Process: 12357 ExecStart=/usr/sbin/amavisd -c
/etc/amavisd/amavisd.conf (code=exited, status=0/SUCCESS)
CGroup: /system.slice/amavisd.service
├─12358 /usr/sbin/amavisd (master)
├─12382 /usr/sbin/amavisd (virgin child)
├─12383 /usr/sbin/amavisd (virgin child)
├─12384 /usr/sbin/amavisd (virgin child)
├─12385 /usr/sbin/amavisd (virgin child)
├─12386 /usr/sbin/amavisd (virgin child)
├─12387 /usr/sbin/amavisd (virgin child)
├─12388 /usr/sbin/amavisd (virgin child)
├─12389 /usr/sbin/amavisd (virgin child)
├─12390 /usr/sbin/amavisd (virgin child)
├─12391 /usr/sbin/amavisd (virgin child)
├─12392 /usr/sbin/amavisd (virgin child)
├─12393 /usr/sbin/amavisd (virgin child)
├─12394 /usr/sbin/amavisd (virgin child)
├─12395 /usr/sbin/amavisd (virgin child)
├─12396 /usr/sbin/amavisd (virgin child)
├─12397 /usr/sbin/amavisd (virgin child)
├─12398 /usr/sbin/amavisd (virgin child)
├─12399 /usr/sbin/amavisd (virgin child)
├─12400 /usr/sbin/amavisd (virgin child)
├─12401 /usr/sbin/amavisd (virgin child)
├─12402 /usr/sbin/amavisd (virgin child)
├─12403 /usr/sbin/amavisd (virgin child)
├─12404 /usr/sbin/amavisd (virgin child)
├─12405 /usr/sbin/amavisd (virgin child)
└─12406 /usr/sbin/amavisd (virgin child)

Mar 30 15:09:19 mail.bordengrammar.kent.sch.uk amavis[12404]: entered
child_init_hook
Mar 30 15:09:19 mail.bordengrammar.kent.sch.uk amavis[12403]:
SpamControl: init_child on SpamAssassin done
Mar 30 15:09:19 mail.bordengrammar.kent.sch.uk amavis[12405]:
Net::Server: Child Preforked (12405)
Mar 30 15:09:19 mail.bordengrammar.kent.sch.uk amavis[12405]: entered
child_init_hook
Mar 30 15:09:19 mail.bordengrammar.kent.sch.uk amavis[12358]:
Net::Server: Parent ready for children.
Mar 30 15:09:19 mail.bordengrammar.kent.sch.uk amavis[12404]:
SpamControl: init_child on SpamAssassin done
Mar 30 15:09:19 mail.bordengrammar.kent.sch.uk amavis[12406]:
Net::Server: Child Preforked (12406)
Mar 30 15:09:19 mail.bordengrammar.kent.sch.uk amavis[12406]: entered
child_init_hook
Mar 30 15:09:19 mail.bordengrammar.kent.sch.uk amavis[12405]:
SpamControl: init_child on SpamAssassin done
Mar 30 15:09:19 mail.bordengrammar.kent.sch.uk amavis[12406]:
SpamControl: init_child on SpamAssassin done


Any mail processed during the restart seems to get bounced but amavisd
picks up where it left off and carries on working until the next restart
which is about 1-2 minutes after.

Any ideas would be helpful. I've been going through logs but can't find
anything that screams "problem's here".

Thanks,

Jools
Stephen Davies
2016-03-31 23:56:50 UTC
Permalink
Post by Julian Pilfold-Bagwell
Hi All,
I have amavisd-new, clamav and spamassassin running alongside postfix
and cyrus and I have a situation where restarting amavisd using
systemctl doesn't exit you to the command prompt, it just waits for ages
Job for amavisd.service failed because a timeout was exceeded. See
"systemctl status amavisd.service" and "journalctl -xe" for details.
amavisd.service - Amavisd-new is an interface between MTA and content
checkers.
Loaded: loaded (/usr/lib/systemd/system/amavisd.service; enabled;
vendor preset: disabled)
Active: activating (start) since Wed 2016-03-30 15:09:11 BST; 42s ago
Docs: http://www.ijs.si/software/amavisd/#doc
Process: 12357 ExecStart=/usr/sbin/amavisd -c
/etc/amavisd/amavisd.conf (code=exited, status=0/SUCCESS)
CGroup: /system.slice/amavisd.service
├─12358 /usr/sbin/amavisd (master)
├─12382 /usr/sbin/amavisd (virgin child)
├─12383 /usr/sbin/amavisd (virgin child)
├─12384 /usr/sbin/amavisd (virgin child)
├─12385 /usr/sbin/amavisd (virgin child)
├─12386 /usr/sbin/amavisd (virgin child)
├─12387 /usr/sbin/amavisd (virgin child)
├─12388 /usr/sbin/amavisd (virgin child)
├─12389 /usr/sbin/amavisd (virgin child)
├─12390 /usr/sbin/amavisd (virgin child)
├─12391 /usr/sbin/amavisd (virgin child)
├─12392 /usr/sbin/amavisd (virgin child)
├─12393 /usr/sbin/amavisd (virgin child)
├─12394 /usr/sbin/amavisd (virgin child)
├─12395 /usr/sbin/amavisd (virgin child)
├─12396 /usr/sbin/amavisd (virgin child)
├─12397 /usr/sbin/amavisd (virgin child)
├─12398 /usr/sbin/amavisd (virgin child)
├─12399 /usr/sbin/amavisd (virgin child)
├─12400 /usr/sbin/amavisd (virgin child)
├─12401 /usr/sbin/amavisd (virgin child)
├─12402 /usr/sbin/amavisd (virgin child)
├─12403 /usr/sbin/amavisd (virgin child)
├─12404 /usr/sbin/amavisd (virgin child)
├─12405 /usr/sbin/amavisd (virgin child)
└─12406 /usr/sbin/amavisd (virgin child)
Mar 30 15:09:19 mail.bordengrammar.kent.sch.uk amavis[12404]: entered
child_init_hook
SpamControl: init_child on SpamAssassin done
Net::Server: Child Preforked (12405)
Mar 30 15:09:19 mail.bordengrammar.kent.sch.uk amavis[12405]: entered
child_init_hook
Net::Server: Parent ready for children.
SpamControl: init_child on SpamAssassin done
Net::Server: Child Preforked (12406)
Mar 30 15:09:19 mail.bordengrammar.kent.sch.uk amavis[12406]: entered
child_init_hook
SpamControl: init_child on SpamAssassin done
SpamControl: init_child on SpamAssassin done
Any mail processed during the restart seems to get bounced but amavisd
picks up where it left off and carries on working until the next restart
which is about 1-2 minutes after.
Any ideas would be helpful. I've been going through logs but can't find
anything that screams "problem's here".
Thanks,
Jools
This sounds exactly like the behaviour I saw here until I stopped using
systemctl to start amavisd.

I can't see why systemctl makes amavisd restart every minute or so but
starting amavisd directly makes it behave normally.

Cheers,
Stephen
--
=============================================================================
Stephen Davies Consulting P/L Phone: 08-8177 1595
Adelaide, South Australia. Mobile:040 304 0583
Loading...