ClamD Service Failed to Start? We can help you.

As part of our Server Management Services, we assist our customers with several such errors.

Today, let us see how our techs fix this error for our customers.

ClamD Service Failed to Start

Most often ClamD service fails to start with the following error:

Startup Log
LibClamAV Error: cli_tgzload: Invalid checksum for file daily.hsb
LibClamAV Error: Can’t load /usr/local/cpanel/3rdparty/share/clamav/daily.cld: Malformed database
ERROR: Malformed database

This error indicates that the database file daily.cld for the ClamAV virus definitions has become corrupt and cannot load during startup.

Generally, such an incident occurs if the data files have been unexpectedly altered.

On the other hand, a premature interruption of an update through freshclam can also lead to this error.

In order to repair the database, first, we need to move the current database files out of the way. We do this so that we can recreate it.

Using the above error example, the below command will move the file daily.cld to a backup location using the current date.

However, if the startup error references a different file, we need to move that one instead.

mv /usr/local/cpanel/3rdparty/share/clamav/daily.cld{,.$( date +%Y%m%d )}

Once we move the corrupt database file, we will need to initiate a freshclam to download the updated database information to rebuild it.

/usr/local/cpanel/3rdparty/bin/freshclam

Eventually, the service will start normally via the restartsrv command given below:

/scripts/restartsrv_clamd

[Stuck in between? We’d be glad to help you out]

Conclusion

In short, we saw how our Support Techs fix the ClamD error quickly.