Clamd error messages since last week

[Paul Welsh]

Following on from my issues with clamd, I rebooted the server and the
errors stopped for several weeks, then came back again.  I rebooted again
today.

I restart the daemon each time it fails but once it starts failing,
restarts don't have any long lasting effect.  When I say long lasting, the
errors start again within the hour.

Anyone else getting this?  I'm running version 0.98.4.

On 30 August 2014 12:00, <mailscanner-request at lists.mailscanner.info> wrote:

>
> ---------- Forwarded message ----------
> From: Paul Welsh <paul at welshfamily.com>
> To: MailScanner discussion <mailscanner at lists.mailscanner.info>
> Cc:
> Date: Fri, 29 Aug 2014 19:13:31 +0100
> Subject: Re: Clamd error messages since last week
>
>> If the clamd daemon is local to the mailscanner machine I would recommend
>> switching to a unix socket instead of tcp. Set it in your clamd.conf and
>> then mirror the path and filename in the MailScanner.config such as
>> Clamd Socket = /tmp/clamd
>>
>> Also I attached a small perl script that will check clamd and make sure
>> it's both up and running and capable of responding (the PING/PONG)
>> anything you can use to monitor program result codes can use this as it
>> returns 0 for OK and 1 for any issues, you can also have it log to
>> mail|info if you want to use a log file analizer and just call it from cron
>> ever min or so, there is very, very little overhead
>>
>> Rick Cooper
>>
>>
> Thanks for responding, Rick.  Seems to be setup that way already though:
>
> # grep 'Clamd Socket' /etc/MailScanner/MailScanner.conf
> Clamd Socket = /var/run/clamav/clamd.sock
>
> # grep LocalSocket /etc/clamd.conf
> LocalSocket /var/run/clamav/clamd.sock
>
> Suppose a reboot is the next step.  Upgrading to ClamAV 0.98.4 made no
> difference.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20140921/2fd6734d/attachment.html