Clamd: ERROR: Unable to lock database directory!

[zibra]

I have some problems on zcs OSS 4.5.9 about clamd. Recently, my clamd usually happens the following error:
ERROR: reload db failed: Unable to lock database directory
Terminating because of a fatal error.
Pid file removed.

and when i use "zmcontrol status" and receive "zmclamdctl is not running".

I stop zimbra and start again, the system operates normally for some minutes. Each time, clamd reloads database from /opt/zimbra/clamav/db, the problem will happen.
I wonder if they have any bugs in clamav.

Thanks for regard.

[uxbod]

could you check the permissions on /opt/zimbra/clamav/db please.

they may be incorrect and require a zmfixperms to sort it out. would also make sure all other permissions are correct aswell.

[zibra]

I don't think that is my problem. The permission is right. I realize that: when i start zimbra, it start normally, clamd is loaded. But each time, the system reloads database of clamd automatically, this error happen.

[uxbod]

found this on a mailing list :-

> this night my clamd-process terminated with an error. The reason was
> that freshclam took too long to do its update, so that clamd could not
> lock the database. So clamd exited. But this behaviour is very fatal
> because the mail system (postfix with amavis) relys on clamd, so if it
> is down, the whole mail traffic is blocked!! Caused of an error while
> updating......
>

is this happening then just after freshclam runs ?

[zibra]

I think this is the problem which i 'm encountering. At present, i don't permit clamav to update from internet. So, if you have any ways to prevent freshclam from taking too long to to its updates.

Many thanks,