[SOLVED] ClamAV too slow to start for cluster

[Klug]

I'm currently playing with a cluster and I have a very strange (and PITA because Zimbra won't start) behaviour since yesterday.

I've stopped the cluster (to upgrade ILO firmware to try ILO fencinf instead of APC fencing).

Then launched it again.

rgmanager launches "zmcluctl start", the zimbra services start "nicely".
then it launches "zmcluctl status" but this one returns a "not running" value
so rgmanager stops the service and tries to put in on the other node
where the same thing happens
etc

I've stopped the second node and rgmanager and tried to launch zimbra by hand.

This way, I was able to do several "zmcluctl status" right after the start.
"zmcluctl status" says it's zmclamdctl that is not running.
But if I wait a bit more (30 seconds more than rmanager waits before launching the status test), "zmcluctl status" says it's correctly running.

So, since a couple of days (I noticed it yesterday after a reboot but it might be older), clamd is just too slow to start (at least for rgmanager).

I had a quick look at ClamAV 0.91rc2 release notes and it seems to be a known problem on their side : "improved handling of .mdb files (fixes long startup times)" as seen here : WebSVN - clamav-devel - Rev 3110 - /trunk/README

Until ClamAV is updated in Zimbra, is there any way to "slow" rgmanager (or cheat on first status test) ?

[babou]

I have this problem too, do you try updating to new clamav version ?

[mmorse]

He did -this is an older thread- see his 2 posts here: /forums/installation/9268-solved-clamav-problem-whats-happening-3.html

[Klug]

A croire que tous les clusters Zimbra sont en France 8)

Yes, upgrading to 4.5.7 fixed the ClamAV issue.

If you don't want to upgrade the whole cluster (that's the official and supported way), you can upgrade ClamAV alone (on each node, obviously), it'll fix the issue too.

Marking the thread as solved, as I should have done it before 8-/

[babou]

Originally Posted by mmorse

He did -this is an older thread- see his 2 posts here: /forums/installation/9268-solved-clamav-problem-whats-happening-3.html

thanks, I 've seen it too late

Originally Posted by Klug

A croire que tous les clusters Zimbra sont en France 8)

Yes, upgrading to 4.5.7 fixed the ClamAV issue.

If you don't want to upgrade the whole cluster (that's the official and supported way), you can upgrade ClamAV alone (on each node, obviously), it'll fix the issue too.

Marking the thread as solved, as I should have done it before 8-/

Effectivement

We are going to migrate soon .... in a few week
Do you know if i can upgrade properly on 4.5.4 to 4.5.7 or do I have to upgrade to 4.5.5 and 4.5.6 before ?

[mmorse]

you can certainly skip versions (though there were more ldap/tomcat changes between .6 & .7 than any of the other subversion of late)

[Klug]

We did 4.5.5 to 4.5.7 on this cluster, no problem at all.