Quote:
Originally Posted by mlissner  Thanks for the help - I hadn't realized that was my first post. I guess I had been thinking about posting for a little while. |
I saw you were a member since Sept 21st though
Quote:
Originally Posted by mlissner You're right, the mail is going to the deferred queue as of now. As for error messages you're right on the money. I guess that means that I'm making some beginner's mistake, but I don't understand what that message means.
Am I missing something? Thanks. |
Nope it's not your fault, make a backup & upgrade to 4.5.7
SourceForge.net: Files or .8
/community/downloads.html
The clamav version in 4.5.6 needed some fixing. In-short you end up in a clamav restart loop, hence why I first suggested changing the watchdog timeout.
Optionally you can also update manually, again make a backup and see
Updating CLAMAV - ZimbraWiki Quote:
Originally Posted by mlissner I upped the value in the zmmtaconfig file to 320, restarting the server, and checked the status of the server, and antivirus still wasn't running, so I made a clamd.pid file in /opt/zimbra/log/, via touch /opt/zimbra/log/clamd.pid, but that didn't do the trick either. |
If you want to keep trying with the .pid - though if you're already not getting any luck past 5 min I doubt it will help...
Backup the /opt/zimbra/bin/zmantivirusctl file
As the zimbra user create /opt/zimbra/log/clamd.pid.fake
Then as root, in /opt/zimbra/bin/zmantivirusctl right after the line
Code:
/opt/zimbra/bin/$i start norewrite
insert
Code:
cp /opt/zimbra/log/clamd.pid.fake /opt/zimbra/log/clamd.pid
so that everytime clamav starts it creates the clamd.pid file from clamd.pid.fake
If you we're curious, one of the bugs was here:
Bug 18312 - ClamAV: clamd corrupt db
The most succinct summary:
Quote:
|
One theory is that since clamAV 0.90 has a very long start-up, and zmmtaconfig/watchdog runs once a minute, it's entirely possible that corruptions are happening when a second clamAV is started. So getting a faster start-up (0.91.1) may fix this.
|