frenziedfox

Active Member
Mar 9, 2010
27
4
53
Hi,

When I woke up this morning I had loads of clamd FAILED emails! For the time being I have switched the email off for clamd.

I tried a manual restart:

Service “clamd” is already stopped.

Waiting for “clamd” to start ……info [restartsrv_clamd] systemd failed to start the service “clamd” (The “/usr/bin/systemctl restart clamd.service --no-ask-password” command (process 21044) reported error number 1 when it ended.): Job for clamd.service failed because the control process exited with error code. See "systemctl status clamd.service" and "journalctl -xe" for details.

…failed.

Cpanel::Exception::Services::StartError
Service Status

Service Error
(XID pbf2rs) The “clamd” service failed to start.

Startup Log
Apr 06 07:28:47 matthae3.miniserver.com systemd[1]: Starting clamd antivirus daemon...
Apr 06 07:29:04 matthae3.miniserver.com systemd[1]: clamd.service: control process exited, code=exited status=1
Apr 06 07:29:04 matthae3.miniserver.com systemd[1]: Failed to start clamd antivirus daemon.
Apr 06 07:29:04 matthae3.miniserver.com systemd[1]: Unit clamd.service entered failed state.
Apr 06 07:29:04 matthae3.miniserver.com systemd[1]: clamd.service failed.

clamd has failed. Contact your system administrator if the service does not automagically recover.
Anyone know what to do?

thanks,

Alex
 

frenziedfox

Active Member
Mar 9, 2010
27
4
53
Well I ended up removing the plugin, moving /usr/local/cpanel/3rdparty/share/clamav to clam.old, re-installing Clam plugin and now it's running.

● clamd.service - clamd antivirus daemon
Loaded: loaded (/etc/systemd/system/clamd.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2020-04-06 11:18:11 BST; 4min 2s ago
Process: 31542 ExecStart=/usr/local/cpanel/3rdparty/bin/clamd (code=exited, status=0/SUCCESS)
Main PID: 31544 (clamd)
CGroup: /system.slice/clamd.service
└─31544 /usr/local/cpanel/3rdparty/bin/clamd
 

cPanelLauren

Product Owner
Staff member
Nov 14, 2017
13,304
1,252
313
Houston
Hello,

I'm glad to see you were able to resolve the issue but should this occur again it would be good to know what caused it. You should be able to find some information within /usr/local/cpanel/logs/error_log should you run into any further issues.