tim.taylor at gmail.com
Sun Jun 25 11:41:50 CEST 2017
On further investigation, the amavisd-new cron job was failing with return
code 3 because the file /var/run/amavis/amavisd.pid did not exist (although
amavisd.lock did exist in that directory).
Permissions of the directories looked fine, but restarting the amavisd-new
daemon did not solve the problem (still no amavisd.pid file).
As a last resort I rebooted the server... and this seems to have fixed the
problem. The .pid file is now there, and the cron job works without error.
I don't know what caused this error (I see that the lastest version of
amavisd-new does include various changes to how .pid files are handled, but
I don't know if that has any bearing on my problem). Anyhow, it's all fixed
On 22 June 2017 at 10:19, Tim Taylor <tim.taylor at gmail.com> wrote:
> and Spamassassin 3.4.1 (running on Perl 5.22.1)
> On 22 June 2017 at 10:18, Tim Taylor <tim.taylor at gmail.com> wrote:
>> I should have added, I'm running:
>> Ubuntu 16.04
>> Postfix 3.1.0
>> amavisd-new 2.10.1
>> On 22 June 2017 at 10:11, Tim Taylor <tim.taylor at gmail.com> wrote:
>>> Hi. For the last couple of days I've been getting the following errors
>>> reported by spamassassin:
>>> run-parts: /etc/spamassassin/sa-update-hooks.d/amavisd-new exited with return code 3
>>> run-parts: /etc/cron.daily/spamassassin exited with return code 1
>>> Is this a temporary problem or is it something requiring action on my part?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the amavis-users