severity 420593 important thanks This one time, at band camp, Maurice Massar said: > Severity: grave > Justification: causes non-serious data loss
Temp failing mail isn't the same as data loss. I agree it is important, and I'm looking at it now. > clamav-daemon has repeatedly gone in a loop eating 100% CPU > and not answering any queries anymore. Only kill -9 could > terminate it. > > I just looked into it with strace: > > --- SIGSEGV (Segmentation fault) @ 0 (0) --- > sigreturn() = ? (mask now ~[HUP INT KILL SEGV > USR2 PIPE TERM STOP RTMIN]) > --- SIGSEGV (Segmentation fault) @ 0 (0) --- > sigreturn() = ? (mask now ~[HUP INT KILL SEGV > USR2 PIPE TERM STOP RTMIN]) > ... repeated endless ... > > I've no idea what causes the initial segv, but this loop > blocks all clients accessing clamd, in my case all incoming > mail. On my 3 MX hosts (combined 150k mails / day) it happens > roughly once a week (and sadly not all MTAs do a fallback > on a secondary MX). > > I already had this problem with 0.90.1-0volatile1, > if I remember correctly. Can you install clamav-dbg, attach gdb to the process, and send me a full backtrace? If you're not sure how to do that, let me know and I'll provide instructions. Thanks very much, -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [EMAIL PROTECTED] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
signature.asc
Description: Digital signature