>>>>> "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.
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.
>>> After removing the clamav-unofficial-sigs cron job, last night clamd
>>> got stuck using all cpu. (800% on the 8-node box.)
AC> Again, please provide the logs mentioned above.
Again there nothing was logged to clamd.log.
-JimC
--
James Cloos <cl...@jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
