When max stream is reached, ClamD seems to stop itself (I can repeat
with my test case.)
Test case, create a mail that is larger than max stream.
Using STREAM from TCP/IP socket, I send the entire 20MB file (max stream
is ~ 10MB.)
I know I can set this in my calling program, but ClamD shouldn't die (is
a DOS issue?)
Here is the last few log lines (clamd was freshly started, and nothing
else has been scanned)
Thu Mar 2 13:27:36 2006 -> Self checking every 1800 seconds.
Thu Mar 2 13:41:31 2006 -> WARNING: ScanStream: Size limit reached (
max: 10485760)
Thu Mar 2 13:42:07 2006 -> WARNING: ScanStream: Size limit reached (
max: 10485760)
Thu Mar 2 13:42:38 2006 -> Pid file removed.
Thu Mar 2 13:42:39 2006 -> Exiting (clean)
Thu Mar 2 13:42:39 2006 -> --- Stopped at Thu Mar 2 13:42:39 2006
Two separate boxes have this issue, installed from RPM
clamd.conf
LogFile /var/log/clamd.log
LogFileUnlock
LogTime
LogClean
FixStaleSocket
TCPSocket 3310
TCPAddr 192.168.0.4
SelfCheck 3600
User clamav
What isn't visible is at its default (commented out.)
I saw a config parameter that said if libclamav reported out of memory,
to shutdown. Is this the one that is causing the issue?
Setting StreamMaxLength to a greater values does solve the restarting.
My boxes:
BoxA: Linux printservera.truss.truss 2.6.15-1.1831_FC4 #1 Tue Feb 7
13:37:42 EST 2006 i686 i686 i386 GNU/Linux
free:
total used free shared buffers cached
Mem: 320960 264468 56492 0 23028 74112
-/+ buffers/cache: 167328 153632
Swap: 393208 64 393144
clamd -V:
ClamAV 0.88/1310/Thu Mar 2 13:01:25 2006
BoxB:
Linux mysqlsa 2.4.20-43.9.legacy #1 Sat Apr 30 19:18:42 EDT 2005 i686
i686 i386 GNU/Linux
free:
total used free shared buffers cached
Mem: 255304 231600 23704 0 33672 47916
-/+ buffers/cache: 150012 105292
Swap: 1020116 189552 830564
clamd -V:
ClamAV 0.88/1310/Thu Mar 2 13:01:25 2006
--
Thanks in advance,
James
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
