On Thu, 15 Jul 2010 17:35:49 -0700 Jim Preston <jimli...@commspeed.net> wrote:
> On Jul 15, 2010, at 5:14 PM, Jim Preston wrote: > > > > > On Jul 15, 2010, at 1:40 PM, Török Edwin wrote: > > > >> On Thu, 15 Jul 2010 16:22:49 -0400 > >> Shawn Bakhtiar <shashan...@hotmail.com> wrote: > >> > >>> > >>> > >>> having a sinister problem. > >>> > >>> I have modfied a SysV script to start the clamd and than clam- > >>> milter. > >>> when I check status I get: > >>> > >>> [r...@smtp ~]# /etc/init.d/clamav-milter status > >>> clamav-milter (pid 3432) is running... > >>> clamd (pid 3426) is running... > >>> > >>> I send an email and the header has : > >>> > >>> X-Virus-Status: Clean > >>> X-Virus-Scanned: clamav-milter 0.96 at smtp.inksystemsinc.com > >>> > >>> > >>> > >>> I come back a few days later and I get this: > >>> > >>> [r...@smtp ~]# /etc/init.d/clamav-milter status > >>> clamav-milter dead but subsys locked > >>> clamd (pid 5152) is running... > > > > This is very similar to what I get with my mail server. Seemed to > > be happening every time freshclam ran which is handled via a cron > > task. I could not figure out was was causing it and just went to a > > workaround of having a cron task restart of the clamav-milter 2 > > min after the freshclam task. > > > > I will be happy to try any solutions that get posted here > > regarding a fix for this. It is a personal test mail server so I am > > not terribly concerned about having > > the restart task. > > > > Thanks, Jim_______________________________________________ > > > > Edwin, > > This may have nothing to do with Shawn's problem but ...... > > Could this be a problem with SELinux on my system? > /var/log/clamav-milter.log.scan:audit/audit.log:type=ANOM_ABEND > msg=audit(1264972228.023:953): auid=4294967295 uid=46 gid=46 > subj=root:system_r:unconfined_t:s0-s0:c0.c1023 pid=25871 > comm="clamav- milter" sig=25 > > I do get this in the audit log ....... That doesn't look like an SELinux message (they are all AVC something...), rather it looks like it just logs the fact that the milter crashed. So yes it might be the same problem as Shawn's. Do you have core files enabled? Did it leave a core file behind? You could also try to attach gdb to clamav-milter, and get a stacktrace when it crashes: # gdb /usr/sbin/clamav-milter `pidof clamav-milter` ... (gdb) continue ..... SIGSEGV .... (gdb) thread apply bt full Best regards, --Edwin _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
