Zimbra

d64 · #1 (**permalink**) 10-10-2008, 04:11 AM

Running zimbra-core-4.5.10_GA_1575.FC5-20071117095155 here, as there's no Finnish translation of v5 yet, and I've the following problem..

The clamd process gets stuck a lot. First I get an alert that mail is not going anywhere, and in "top" I can see the clamd process taking all CPU. It will never stop (at least it can run all night without getting anywhere), and it will not even die with simple kill, only kill -9 will do.

The log looks something like this. There's nothing further after the disconnects.

Code:

Fri Oct 10 12:46:50 2008 -> /opt/zimbra/amavisd/tmp/amavis-20081010T123021-24644/parts/p002: HTML.Phishing.Bank-1272 FOUND
Fri Oct 10 12:56:12 2008 -> No stats for Database check - forcing reload
Fri Oct 10 12:56:12 2008 -> Reading databases from /opt/zimbra/clamav/db
Fri Oct 10 12:56:44 2008 -> Database correctly reloaded (578243 signatures)
Fri Oct 10 13:00:51 2008 -> Client disconnected
Fri Oct 10 13:00:51 2008 -> Client disconnected
Fri Oct 10 13:00:51 2008 -> Client disconnected
Fri Oct 10 13:00:51 2008 -> Client disconnected
Fri Oct 10 13:00:51 2008 -> Client disconnected
Fri Oct 10 13:00:51 2008 -> Client disconnected
Fri Oct 10 13:00:51 2008 -> Client disconnected
Fri Oct 10 13:00:51 2008 -> Client disconnected
Fri Oct 10 13:00:51 2008 -> Client disconnected
Fri Oct 10 13:00:51 2008 -> Client disconnected
Fri Oct 10 13:00:51 2008 -> Client disconnected
Fri Oct 10 13:00:51 2008 -> Client disconnected
Fri Oct 10 13:01:15 2008 -> Client disconnected
Fri Oct 10 13:01:15 2008 -> Client disconnected
Fri Oct 10 13:01:37 2008 -> Client disconnected
Fri Oct 10 13:01:46 2008 -> Client disconnected
Fri Oct 10 13:01:50 2008 -> Client disconnected
Fri Oct 10 13:01:59 2008 -> Client disconnected
Fri Oct 10 13:02:00 2008 -> Client disconnected

Any clues?

d64 · #2 (**permalink**) 10-21-2008, 01:31 AM

Is it possible that this might have been related to the stats being broken? The stats SQL was "stuck" and I had to rebuild it with repair table use_frm, bringing it's size down from over 10 gigs to about 400m too, and since then the clamd problem has not happened?