Description of problem: Each morning when the /usr/share/spamassassin/sa-update.cron script is run, one step is to issue this command: [ -f /run/amavis/amavis.pid ] && /usr/bin/systemctl reload amavisd >& /dev/null The result is that the amavisd daemon crashes Version-Release number of selected component (if applicable): 2.8.2-0.rc1.4 How reproducible: Every time Steps to Reproduce: 1. $ sudo systemctl reload amavisd 2. $ sudo systemctl status amavisd amavisd.service - AMAVIS interface between MTA and content checkers Loaded: loaded (/usr/lib/systemd/system/amavisd.service; enabled) Active: failed (Result: exit-code) since Thu 2014-02-13 08:52:03 CST; 1s ago Process: 585 ExecReload=/usr/sbin/amavisd -c /etc/amavisd/amavisd.conf -P /run/amavis/amavis.pid reload (code=exited, status=0/SUCCESS) Process: 32562 ExecStart=/usr/sbin/amavisd -c /etc/amavisd/amavisd.conf -P /run/amavis/amavis.pid (code=exited, status=0/SUCCESS) Main PID: 32563 (code=exited, status=13) Feb 13 08:52:03 ns1.austinnetworkdesign.com amavis[585]: Valid PID file (younger than sys uptime 4 13:34:00) Feb 13 08:52:03 ns1.austinnetworkdesign.com amavis[585]: Signalling a SIGHUP to a running daemon [32563] Feb 13 08:52:03 ns1.austinnetworkdesign.com amavis[32563]: Net::Server: Received a SIG HUP Feb 13 08:52:03 ns1.austinnetworkdesign.com amavisd[585]: Signalling a SIGHUP to a running daemon [32563] Feb 13 08:52:03 ns1.austinnetworkdesign.com amavis[32563]: Net::Server: 2014/02/13-08:52:03 Server closing! Feb 13 08:52:03 ns1.austinnetworkdesign.com amavis[32563]: Net::Server: Sending children hup signal Feb 13 08:52:03 ns1.austinnetworkdesign.com amavis[32563]: (!)Net::Server: 2014/02/13-08:52:03 Re-exec server during HUP Feb 13 08:52:03 ns1.austinnetworkdesign.com systemd[1]: Reloaded AMAVIS interface between MTA and content checkers. Feb 13 08:52:03 ns1.austinnetworkdesign.com systemd[1]: amavisd.service: main process exited, code=exited, status=13/n/a Feb 13 08:52:03 ns1.austinnetworkdesign.com systemd[1]: Unit amavisd.service entered failed state. Reproducible: Steps to Reproduce:
Summary: systemdctl reload amavisd causes daemon to crash => systemctl reload amavisd causes daemon to crash
Keywords: (none) => TriagedAssignee: bugsquad => thomas
Yeah I am seeing this problem too. Will try and work out why.
CC: (none) => mageia
Got it. The /etc/amavisd/amavisd.conf file needs to be group owned+readable by amavis user. Out of the box, this is how the RPM is configured, but my system got out of sync at some point over the years. I got the hint from this post: http://lists.amavis.org/pipermail/amavis-users/2012-July/001738.html After correcting this, the reload works fine.
Status: NEW => RESOLVEDResolution: (none) => INVALID
I've closed this bug but I've also added a workaround in the package and submitted it to updates/testing. All it does is do a chgrp+chmod in the %post - nothing too complex! As we've got an update pending already for MGA3, I've (currently) bundled it in there so the update will come through bug #11246 (unless QA want to keep it separate in which case this bug will likely be reopened). All the best.