On Thu, 22 Apr 2010, jef moskot wrote:
Things ran smoothly for a little while without the larger databases...
Hmm, looks like I spoke too soon. While it did catch bad messages, it
barfed a little while doing so.
A couple of examples...
===
libclamav JIT: Allocation failed when allocating new memory in the JIT
^[[0;1;31mlibclamav JIT: *** FATAL error encountered during bytecode generation
^[[0m./Work/INPUTMBOX: Sanesecurity.Junk.9210.UNOFFICIAL FOUND
===
libclamav JIT: Allocation failed when allocating new memory in the JIT
^[[0;1;31mlibclamav JIT: *** FATAL error encountered during bytecode generation
^[[0mLibClamAV Warning: fmap: map allocation failed
LibClamAV Warning: fmap: map allocation failed
LibClamAV Error: CRITICAL: fmap() failed
LibClamAV Warning: fmap: map allocation failed
LibClamAV Error: CRITICAL: fmap() failed
LibClamAV Warning: fmap: map allocation failed
LibClamAV Error: CRITICAL: fmap() failed
./Work/INPUTMBOX: local.sig.939.UNOFFICIAL FOUND
===
clamscanning from the command line doesn't seem to cause this problem.
Maybe because it's doing something funky decoding mail messages when
launched from mimedefang, as opposed to regular files sitting in a
directory? Scanning mbox files from the command line doesn't seem to
cause these errors.
Jeffrey Moskot
System Administrator
j...@math.miami.edu
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
