On 04/22/2010 01:02 PM, jef moskot wrote: > 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
You are running out of memory (or rather mmap()s). We have a bugreport about this, but we haven't figured how to fix it. Increasing the max number of mmaps FreeBSD allows won't fix it :( > 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. Try scanning the same file mimedefang scans. Best regards, --Edwin _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
