[clamav-users] Unable to start clamd daemon

[vze1amckv at verizon.net]

I apologize if the answer to my question is obvious from your original 
post.  Although I can see you're running it in the cloud, what 
distribution/flavor/version of operating system are you using?

Meanwhile, please feel free to post the output of the "clamconf" 
command.  Thank you.

On 6/24/21 8:04 PM, Lopez, Carmelo via clamav-users wrote:
> Hello,
> 
> I am new to clamav and I’ve completed installing a private mirror 
> server. Freshclam works fine but when I try to start the clamd daemon I 
> get this error. Any help is appreciated.
> 
> systemctl status clamd at scan -l
> 
> ● clamd at scan.service - clamd scanner (scan) daemon
> 
>     Loaded: loaded (/usr/lib/systemd/system/clamd at scan.service; enabled; 
> vendor preset: disabled)
> 
>     Active: failed (Result: start-limit) since Thu 2021-06-24 23:21:13 
> UTC; 41min ago
> 
>       Docs: man:clamd(8)
> 
>             man:clamd.conf(5)
> 
>             https://www.clamav.net/documents/
> 
>    Process: 2030 ExecStart=/usr/sbin/clamd -c /etc/clamd.d/%i.conf 
> (code=exited, status=1/FAILURE)
> 
> Jun 24 23:21:13 ip-10-64-205-168.us-west-2.compute.internal systemd[1]: 
> clamd at scan.service: control process exited, code=exited status=1
> 
> Jun 24 23:21:13 ip-10-64-205-168.us-west-2.compute.internal systemd[1]: 
> Failed to start clamd scanner (scan) daemon.
> 
> Jun 24 23:21:13 ip-10-64-205-168.us-west-2.compute.internal systemd[1]: 
> Unit clamd at scan.service entered failed state.
> 
> Jun 24 23:21:13 ip-10-64-205-168.us-west-2.compute.internal systemd[1]: 
> clamd at scan.service failed.
> 
> Jun 24 23:21:13 ip-10-64-205-168.us-west-2.compute.internal systemd[1]: 
> clamd at scan.service holdoff time over, scheduling restart.
> 
> Jun 24 23:21:13 ip-10-64-205-168.us-west-2.compute.internal systemd[1]: 
> Stopped clamd scanner (scan) daemon.
> 
> Jun 24 23:21:13 ip-10-64-205-168.us-west-2.compute.internal systemd[1]: 
> start request repeated too quickly for clamd at scan.service
> 
> Jun 24 23:21:13 ip-10-64-205-168.us-west-2.compute.internal systemd[1]: 
> Failed to start clamd scanner (scan) daemon.
> 
> Jun 24 23:21:13 ip-10-64-205-168.us-west-2.compute.internal systemd[1]: 
> Unit clamd at scan.service entered failed state.
> 
> Jun 24 23:21:13 ip-10-64-205-168.us-west-2.compute.internal systemd[1]: 
> clamd at scan.service failed.
> 
> *Carmelo Lopez*
> 
> Access-CL-Concur US
> 
> *Concur St. Louis Park (MN), *1550 Utica Avenue South, St. Louis Park 
> 55416-5312, United States
> 
> T   +19529471714, M   +16512602626, carmelo.lopez01 at sap.com 
> <mailto:carmelo.lopez01 at sap.com>
> 
> *Please consider the impact on the environment before printing this email.*
> 
> signature_791736281
> 
> 
> 
> _______________________________________________
> 
> clamav-users mailing list
> clamav-users at lists.clamav.net
> https://lists.clamav.net/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml
>