On 2011-08-11 22:02, ulises gonzalez wrote: > On Thursday 11 August 2011 02:29:17 pm Török Edwin wrote: >> How? Is it a SIGSEGV/SIGBUS/something else? > > > Excuse me, how I can do this...??
Following the instructions on the clamav website on how to attach gdb to clamd, then wait for the selfcheck (or trigger it with clamdscan --reload). Then instead of crashing completely it should stop in gdb and tell you _why_ it stopped. > >> Grep your dmesg for messages about clamd (segfaults are usually logged >> there). Also see if clamd created a core file. > > There is nothing in dmesg > > servergrupo:~/clamv-clamuko-squeeze# dmesg | grep clamav > servergrupo:~/clamv-clamuko-squeeze# dmesg | grep clamd > servergrupo:~/clamv-clamuko-squeeze# > >> See here for instructions on how to get a stacktrace: >> http://www.clamav.net/lang/en/bugs/ >> > > I'll do this > >> Then open a bug on bugs.clamav.net. >> >> Also does this happen only if you enable Clamuko in clamd.conf, >> or does it happen if you disable it too? > > No, if I don't enable clamuko it selfcheck correctly > > Thu Aug 11 14:55:59 2011 -> PDF support enabled. > Thu Aug 11 14:55:59 2011 -> HTML support enabled. > Thu Aug 11 14:55:59 2011 -> Self checking every 72 seconds. > Thu Aug 11 14:57:11 2011 -> No stats for Database check - forcing reload > Thu Aug 11 14:57:12 2011 -> Reading databases from /var/lib/clamav > Thu Aug 11 14:57:18 2011 -> Database correctly reloaded (1018481 signatures) > > It only happens with clamuko enabled > _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
