• Welcome to The Network People Support Forums. Please login or sign up.

qmail-scanner clamav clamscan/clamdscan errors - SOLVED

Started by LogicX, September 16, 2004, 05:14:11 AM

Previous topic - Next topic

LogicX

New variation on an http://www.tnpi.biz/support/phpBB/viewtopic.php?p=464&highlight=#464" target="_blank">old theme.

/var/log/messages shows us:
Sep 16 12:52:44 tract kernel: pid 40701 (clamscan), uid 1012: exited on signal 11 (core dumped)

/var/log/maillog:
Sep 16 12:52:45 tract X-Qmail-Scanner-1.23: [tract.imcc.ca109535352448240510] clamscan: corrupt or unknown ClamAV scanner error or memory/resource/perms problem - exit status 0

/var/spool/qmailscan/qmail-queue.log reports:
Thu, 16 Sep 2004 12:52:44 EDT:40741: run /usr/bin/clamscan -r -m --unzip --unrar --unzoo --lha --disable-summary --max-recursion=10 --max-space=100000  /var/spool/qmailscan/tmp/tract.imcc.ca109535356448240741 2>&1Thu, 16 Sep 2004 12:52:44 EDT:40510: --output of clamscan was:/var/spool/qmailscan/tmp/tract.imcc.ca109535352448240510/-_one_of_my_favorite_places.mp3: OKLibClamAV Error: cli_realloc(): Can't re-allocate memory to 2506860 byte.realloc_problem: Cannot allocate memory--Thu, 16 Sep 2004 12:52:44 EDT:40510: error_condition: X-Qmail-Scanner-1.23: clamscan: corrupt or unknown ClamAV scanner error or memory/resource/perms problem - exit status 0


I've already modified some of my settings:
smtpd_max_memory_per_connection = 40            # in megabytes
smtpd_max_connections           = 7
smtpd_max_memory                = 356
qmail_scanner_scanners         = clamdscan,fast_spamassassin

It should be noted I'm running 1.23 of qmail-scanner


Now -- what it seems I've discovered is that -- when I run toaster_setup.pl -s qmail-scanner -- the setup scans for available daemons -- it sees, and lists clamdscan, however it puts clamscan in the @scanner_array and subsequently only includes the clamscan, not the clamdscan subroutines in /var/qmail/bin/qmail-scanner-queue.pl

replacing clamdscan in the scanner_array, and adding in the clamdscan subroutine appears to have rectified the situation I was running into -- it now sends the scanning to the external clamd --- no more memory scaling issues, because clamd is not regulated by the memory size settings that we set in toaster_watcher...  hopefully I'll still be saved by the setting which regulates clamd (clamscan too?) -- to not virus scan more than the first 10MB of attachments.
--- May this post be indexed by spiders, and archived for all to see as my internet epitaph.
http://FPuX.com" target="_blank">http://FPuX.com