On 16 Mar 2007, at 17:20, Zbigniew Szalbot wrote:
Hello,
Do you mean it rejects it or tempfails it? A tempfail is a legitimate
condition when your processes are in a failed state. So too is
reject, but
certainly more drastic and likely to create political
repercussions. Worst
is to silently drop messages.
It tempfails them, which is fine when it does not take too long :)
Thanks!
--
Zbigniew Szalbot
Continuing the 'fatal error' saga,
I also noticed the following in the clamd.log:
"Thu Mar 15 05:08:10 2007 -> SelfCheck: Database modification
detected. Forcing reload.
Thu Mar 15 05:08:11 2007 -> Reading databases from /usr/local/share/
clamav
Thu Mar 15 05:10:21 2007 -> ERROR: reload db failed: Unable to lock
database directory (try 1)
Thu Mar 15 05:12:31 2007 -> ERROR: reload db failed: Unable to lock
database directory (try 2)
Thu Mar 15 05:14:42 2007 -> ERROR: reload db failed: Unable to lock
database directory (try 3)
Thu Mar 15 05:14:42 2007 -> ERROR: reload db failed: Unable to lock
database directory
Thu Mar 15 05:14:42 2007 -> Terminating because of a fatal error.Thu
Mar 15 05:14:42 2007 -> Socket file removed.
Thu Mar 15 05:14:42 2007 -> Pid file removed.
Thu Mar 15 05:14:42 2007 -> --- Stopped at Thu Mar 15 05:14:42 2007"
....but, there were no scheduled Freshclam OR SaneSecurity checks /
downloads at the time the log stated
there was a database modification.
Freshclam runs via cron at 56 mins past each hour.
The SaneSecurity updates run via cron at 3 mins past the hour, 4
times a day.
What would've caused a Database modification at that time, 05:08:10,
then ??
Or is this a silly question...
Yours,
Robert R.
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
