Wondering how to resolve ClamD Fails To Start On CL6 Servers? We can help you.

As part of our Server Management Services, we assist our customers with several cPanel queries.

Today, let us see steps followed by our Support Techs to resolve it.

How to resolve ClamD Fails To Start On CL6 Servers?

ClamD is the open-source standard for mail gateway-scanning software.

It includes a multi-threaded scanner daemon, command-line utilities for on-demand file scanning and automatic signature updates.

It also supports multiple file formats and signature languages, as well as file and archive unpacking.

The application develop for Unix and has third party versions available for AIX, BSD, HP-UX, Linux, macOS, OpenVMS, OSF (Tru64) and Solaris. As of version 0.97.5, ClamAV builds and runs on Microsoft Windows.

Both ClamAV and its updates are made available free of charge.

The ClamD can used for scanning incoming files automatically, without having to scan them manually with ClamD.

Typically, on CL6 servers ClamAV fails to start with the following error message:

/scripts/restartsrv_clamd --start
Service “clamd” is already stopped.
[...............]
Startup Log
/usr/local/cpanel/3rdparty/bin/clamd: error while loading shared libraries: libpcre2-8.so.0: cannot open shared object file: No such file or directory

clamd has failed. Contact your system administrator if the service does not automagically recover.

This usually occurs due to a missing shared library object (libpcre2-8.so.0) file that is require by ClamAV which you can confirm by this:

ldd /usr/local/cpanel/3rdparty/bin/clamd
[...............]
libz.so.1 => /lib64/libz.so.1 (0x00007f64ae2db000)
libpcre2-8.so.0 => not found
libm.so.6 => /lib64/libm.so.6 (0x00007f64ae056000)
[...............]

The libpcre2-8.so.0 shared library file is provided by the pcre2 package.

However that package fails to install as a dependency when ClamAV is installed on the server.

Today, let us discuss about the simple resolution provided by our Support techs for this error:

To get around this issue, you can manually install the missing package and then restart ClamD:

yum install pcre2

/scripts/restartsrv_clamd --start

[Stuck with the similar error? We’d be glad to assist you]

Conclusion

In short, today we saw steps followed by our Support Techs  to resolve the ClamD error.