[clamav-users] Unable to start clamd daemon

[Lee, Raymond]

On Tue, Jun 29, 2021 at 12:59 AM Lopez, Carmelo via clamav-users <
clamav-users at lists.clamav.net> wrote:

> We will have lots of clamav clients so that’s why I built a private
> mirror. I’ve resolved the issue. Apparently selinux was preventing the
> clamd daemon from starting. After disabling it, clamd started fine.
>

Instead of disabling SELinux and losing all the benefits it provides, you
should tell it to allow clamd to run.  As the installation instructions say:

sudo setsebool -P antivirus_can_scan_system 1

Re-enable SELinux and try that to see if clamd will start.


Kind Regards,
Ray



>
>
> *From: *clamav-users <clamav-users-bounces at lists.clamav.net> on behalf of
> G.W. Haywood via clamav-users <clamav-users at lists.clamav.net>
> *Date: *Friday, June 25, 2021 at 11:03 AM
> *To: *Lopez, Carmelo via clamav-users <clamav-users at lists.clamav.net>
> *Cc: *G.W. Haywood <clamav at jubileegroup.co.uk>
> *Subject: *Re: [clamav-users] Unable to start clamd daemon
>
> Hi there,
>
> On Thu, 24 June 2021, Lopez, Carmelo via clamav-users wrote:
>
> > I am new to clamav and I’ve completed installing a private mirror
> > server.
>
> Can you tell us why you need a private mirror?  That's not to say that
> I think you don't need one, but it isn't the place where a newcomer to
> ClamAV would normally start.  To be clear, a private mirror will only
> usually be needed if you have a large number of machines in a single
> network, many or all of which will run ClamAV.  By having a copy of
> the ClamAV database on each machine (and, more importantly, by keeping
> all these individual copies up to date) the many machines might create
> an unnecessarily large load - not only on your Internet connection but
> also on the (Cloudflare) database servers.  Cloudflare might consider
> the load abusive, and, if it did, would respond by blocking connection
> attempts from your public IP address.
>
> If you're having any difficulty, and you don't actually need a private
> mirror, I'd recommend keeping things simpler by getting the database
> updates directly to the machines which are running ClamAV.
>
> >> 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
> >> ...
> >>    Process: 2030 ExecStart=/usr/sbin/clamd -c /etc/clamd.d/%i.conf
> >> (code=exited, status=1/FAILURE)
> >> ...
>
> Can I take it that this command was run on the private mirror server?
>
> On Fri, 25 Jun 2021, Lopez, Carmelo via clamav-users wrote:
>
> > I am running RHEL, Red Hat Enterprise Linux Server release 7.9
> > (Maipo). The output of “clamconf” below: By the way, I am running
> > these commands from the clamav private mirror server.
> >
> > [root at ip-10-64-205-168 bin]# clamconf
> > Checking configuration files in /etc
> > ...
>
> Can you tell us *exactly* how you installed ClamAV (a) on your private
> mirror server and (b) on any other machines?
>
> --
>
> 73,
> Ged.
> PS: My mailing list email address accepts mail only from the list.
>
> _______________________________________________
>
> 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
>
> _______________________________________________
>
> 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
>

-- 
Notice: This email and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they are 
addressed. Any unauthorized review, use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please contact the 
sender by reply e-mail and destroy the message and attachments without 
retaining a copy.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clamav.net/pipermail/clamav-users/attachments/20210629/0c7ecfb5/attachment.htm>