ClamAV DB update leads to **UNCHECKED** in all messages: Difference between revisions
(Created page with "{{BC|Certified}} __FORCETOC__ <div class="col-md-12 ibox-content"> =ClamAV DB Update leads to **UNCHECKED** in all messages = {{KB|{{ZC}}|{{ZCS 8.0}}|{{ZCS 7.0}}||}} {{WIP}}...") |
(No difference)
|
Revision as of 16:39, 22 October 2016
ClamAV DB Update leads to **UNCHECKED** in all messages
Purpose
A recent update to ClamAV's DB causes clam to not start up, leading to emails being marked as '**UNCHECKED**'
This affects ClamAV version 0.97.8, and therefore the Zimbra versions affected are 8.0.6 and below, including 7.x.
- ZCS 8.0.7+, 8.6 and 8.7 are not affected.
Manually regenerating the DB leads to the following error:
[zimbra@zcs806 ~]$ /opt/zimbra/clamav/bin/freshclam --config-file=/opt/zimbra/conf/freshclam.conf ClamAV update process started at Sat Oct 22 18:25:14 2016 WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.97.8-broken-compiler Recommended version: 0.99.2 DON'T PANIC! Read http://www.clamav.net/support/faq Downloading main.cvd [100%] main.cvd updated (version: 57, sigs: 4218790, f-level: 60, builder: amishhammer) Downloading daily.cvd [100%] ERROR: During database load : WARNING: [LibClamAV] mpool_malloc(): Attempt to allocate 8388608 bytes. Please report to http://bugs.clamav.net [...] WARNING: [LibClamAV] mpool_malloc(): Attempt to allocate 8388608 bytes. Please report to http://bugs.clamav.net WARNING: Database successfully loaded, but there is stderr output daily.cvd updated (version: 22410, sigs: 761318, f-level: 63, builder: neo) Downloading bytecode.cvd [100%] bytecode.cvd updated (version: 283, sigs: 53, f-level: 63, builder: neo) Database updated (4980161 signatures) from db.us.clamav.net (IP: 69.163.100.14)
Resolution
The only fix for now is upgrade to at least Zimbra Collaboration 8.0.9, but we encourage you to upgrade to Zimbra Collaboration 8.6 and the latest Patch.
Our Technical Support Engineers might have found a workaround by disable the antivirus:
zmprov ms `zmhostname` -zimbraServiceEnabled antivirus zmcontrol restart
But this workaround will let your Zimbra Collaboration Platform without an Antivirus, and we don't recommend it.
Additional Content
- No related content