Quote:
Originally Posted by mlissner  OK - I think I can do either of these three routes (update clamav, update zimbra or set up the clamd.pid copy trick). I think I will go with the first, but it doesn't sound like your recommendation. I had a heck of a time installing Zimbra the first time, and I'd hate to go through that all over again if it wasn't absolutely necessary. As for the file copy trick, it is quite tempting, but it seems like it would ultimately break as soon as I updated anything, so that doesn't sound like a good fix. |
Upgrading is actually really fast, easy, & and your most reliable bet to get this up as fast as possible.
See the bottom of the release notes for instructions
/pdf/Zimbra OS Release Notes.pdf
4.5.7 also had a bunch of tomcat & ldap stability enhancements - 4.5.8 is just a release under Yahoo's license to appease the lawyers
Quote:
Originally Posted by mlissner Before I go through with updating clamav though, why is it that this problem began in the first place? I had a functional installation at one point...I don't think I did any updating or anything that would have caused this problem... |
I edited my above post & put the original bug link in (probably after you had started replying).
Quote:
Originally Posted by mmorse 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.
| |