Hi.
I've seen the following in clamd logs and it looks like some kind of bug:
Wed Mar 16 15:40:02 2005 -> Reading databases from /usr/local/clamav/db Wed Mar 16 15:40:03 2005 -> Database correctly reloaded (31605 viruses) Wed Mar 16 15:42:03 2005 -> ERROR: ScanStream: accept timeout. Wed Mar 16 15:42:03 2005 -> ERROR: ScanStream: accept timeout. Wed Mar 16 15:42:03 2005 -> ERROR: ScanStream: accept timeout. Wed Mar 16 15:42:03 2005 -> ERROR: ScanStream: accept timeout. Wed Mar 16 15:42:03 2005 -> ERROR: ScanStream: accept timeout. ... and so on, with an 'accept timeout' error for each thread.
This is then repeated two minutes later (presumably after the default 120 second timeout on an accept):
Wed Mar 16 15:44:03 2005 -> ERROR: ScanStream: accept timeout. Wed Mar 16 15:44:03 2005 -> ERROR: ScanStream: accept timeout. Wed Mar 16 15:44:03 2005 -> ERROR: ScanStream: accept timeout. ... and so on, again one per thread.
This repeats every two minutes, apparently until I re-start clamd. I've seen more than one instance of this, and the first error message is always exactly two minutes after the 'Database correctly reloaded' message.
Naturally, this doesn't happen every time the databases are re-read...
I'm using v0.83 on Redhat 8. The client is my own code, but it works fine. I can't actually say whether or not clamd still detects viruses at this point, because I've only seen this on our beta test site, not on my development setup.
Is this a known issue?
I'll try to replicate this in my development environment, but any clues as to what might cause this in the meantime would be appreciated.
Thanks, Colin MacDonald
_______________________________________________ http://lurker.clamav.net/list/clamav-devel.html
