Hi James,
On 19.12.2014 23:07, James Cloos wrote:
"AC" == Andreas Cadhalpun <andreas.cadhal...@googlemail.com> writes:
AC> You mean it crashed?
AC> Please provide excerpts of /var/log/clamav/clamav.log and
AC> /var/log/syslog from around the time of the crashes.
Yes, the clamd process quit, so the milter process was rejecting all
incoming mail with a 4xx try again reply.
In each case the last thing logged to clamav.log before I restarted
clamd was just a
Reading databases from /var/lib/clamav
line.
So it looks like it died during a reload, since:
Database correctly reloaded
did not get logged.
Indeed. It seems like one of the unofficial signature databases caused
clamd to crash during reload. It would be great, if you could determine
which one that was, so that the problem can be reproduced.
AC> If you can reproduce the crashes, please install clamav-dbg and use
AC> gdb to provide a backtrace of the crashes.
I removed the clamav-milter call to keep mail flowing; I'll turn it back
on on one of them this weekend.
Thanks.
Best regards,
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org