I have reproduced this error, and am currently working on a fix.  See https://bugzilla.clamav.net/show_bug.cgi?id=12597.  

We made a change to create PID files before dropping privileges so that an unprivileged user cannot change the PID file and have the service manager kill the wrong process.

Since there are still conditions that could cause the child process initialization to fail, the parent process waits for a signal that the child process is initialized to exit, so that it can report an accurate exit status.  When the child drops privileges, it is not able to send SIGINT to the parent.  I am currently working on a patch to have the parent drop privileges so that it can be signaled by the child.

Thanks,
Andy




From: clamav-users <clamav-users-bounces@lists.clamav.net> on behalf of Michael Orlitzky via clamav-users <clamav-users@lists.clamav.net>
Sent: Friday, August 21, 2020 12:20 PM
To: clamav-users@lists.clamav.net <clamav-users@lists.clamav.net>
Cc: Michael Orlitzky <michael@orlitzky.com>
Subject: Re: [clamav-users] ClamAV 0.103.0 release candidate - systemd service start fails
 
On 2020-08-21 11:29, Arjen de Korte via clamav-users wrote:
>
>>   # ps ax | grep clamd
>>   7436 ?        Ssl    0:25 sbin/clamd
>
>      # ps ax | grep clamd
>      7840 pts/2    S+     0:00 /usr/sbin/clamd --debug
>      7841 ?        Ssl    0:38 /usr/sbin/clamd --debug
>
> Previously I've waited for more than an hour, no change. The process 
> running under root never exits.
>

Ok, I can confirm this! After setting

  User clamav

in clamd.conf, I've seen the root process get stuck as well. That's not
an intended effect of the PID file change.


_______________________________________________

clamav-users mailing list
clamav-users@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