Matus UHLAR - fantomas wrote: >>> check clamd logs >>> > > On 23.12.08 08:58, Robert S wrote: > >> There's nothing in the logs at the time the error occurs. I have however >> discovered some of these in my syslog (see last line): >> > [...] > >> Dec 15 01:00:21 mypc freshclam[1230]: Clamd was NOT notified: Can't connect >> to clamd through /var/run/clamav/clamd.sock >> > [...] > >> Dec 2 12:34:54 mypc clamd[1221]: segfault at 8eec7e8 ip 7f9fc0a5da11 sp >> 7fffc8f19990 error 4 in libclamav.so.5.0.4[7f9fc0a43000+ab000] >> >> Maybe I need a cron job to restart clamd when it dies (like the old days). >> It looks as if clamav-milter runs fine. I'm using clamav-0.94.2 (gentoo). >> >> Any solutions? What is "error 4"? >> > > I have no idea, but something look broken on your system. If upgrading it > won't help, you should check HW, memory at first. > > clamd shouldn't crash... > > I agree that clamd shouldn't crash but......it is certainly not always a hardware issue. I used to have problem with the clamav-milter crashing every day. I added a cron job to restart it. Do not remember which version it was but was in the 0.9.x family. One of the upgrades fixed the problem. Since this happened on only one of my systems, I chalked it up to system specific. Linux 2.6.22.14-72.fc6 #1 SMP Wed Nov 21 15:12:59 EST 2007 i686 athlon i386 GNU/Linux
Best, Jim _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
