Hi Steve, thanks for your help.
I have configured in clamav-milter.conf: ... MilterSocket inet:8893 ClamdSocket unix:/var/run/clamav/clamd.ctl ... Miltersocket is tcp, because postfix frontend servers are running on different machines. Communication between clamav-milter and clamd goes via unix socket (clamd.conf) ... LocalSocket /var/run/clamav/clamd.ctl ... I changed "CommandReadTimeout" from 5 to 30 seconds. The errors in the log disappeared immediately. Now there is only one question for me: why it was working on the old hardware without problems? And why on the new hardware only with an increased timeout? Thanks Urban Am 28.10.2015 um 14:34 schrieb Steve Basford: > > On Wed, October 28, 2015 1:25 pm, Urban Loesch wrote: >> Hi, >> >> >> today I moved my clamav-milter and clamd installation (linux container) >> to a brand new hardware. Know I get this strange errors in the log any 3-5 >> minutes. >> > > Did a quick google... > > https://i-mscp.net/index.php/Thread/9756-ClamAV-plugin-Error-with-Clamav-milter/?postID=38365#post38365 > > https://i-mscp.net/index.php/Thread/9756-ClamAV-plugin-Error-with-Clamav-milter/?postID=38368#post38368 > > > Cheers, > > Steve > Web : sanesecurity.com > Blog: sanesecurity.blogspot.com > > _______________________________________________ > Help us build a comprehensive ClamAV guide: > https://github.com/vrtadmin/clamav-faq > > http://www.clamav.net/contact.html#ml > _______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
