<div dir="ltr">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.<div><br></div><div>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.<br><div><br></div><div>Anyone else getting this? I'm running version 0.98.4.<br><div class="gmail_extra"><br><div class="gmail_quote">On 30 August 2014 12:00, <span dir="ltr"><<a href="mailto:mailscanner-request@lists.mailscanner.info" target="_blank">mailscanner-request@lists.mailscanner.info</a>></span> wrote:</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>---------- Forwarded message ----------<br>From: Paul Welsh <<a href="mailto:paul@welshfamily.com">paul@welshfamily.com</a>><br>To: MailScanner discussion <<a href="mailto:mailscanner@lists.mailscanner.info">mailscanner@lists.mailscanner.info</a>><br>Cc: <br>Date: Fri, 29 Aug 2014 19:13:31 +0100<br>Subject: Re: Clamd error messages since last week<br><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div><div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">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</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">Clamd Socket = /tmp/clamd</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">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)</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">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</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">Rick Cooper</font></span></div></div><div dir="ltr" align="left"><span><font color="#0000ff" face="Arial"><br></font></span></div></blockquote></div></div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Thanks for responding, Rick. Seems to be setup that way already though:</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_extra">
# grep 'Clamd Socket' /etc/MailScanner/MailScanner.conf<br></div><div class="gmail_extra"><div class="gmail_extra">Clamd Socket = /var/run/clamav/clamd.sock</div><div><br></div><div><div># grep LocalSocket /etc/clamd.conf</div>
<div>LocalSocket /var/run/clamav/clamd.sock</div></div><div><br></div><div>Suppose a reboot is the next step. Upgrading to ClamAV 0.98.4 made no difference.</div></div></div></div></blockquote><div><br></div></div></div></div></div></div>