[Pkg-clamav-devel] Bug#996971: systemd: clamav service units fail with StandardOutput=syslog

[Brown, Thomas]

On 10/21/21 4:00 PM, Michael Biebl wrote:
> Am 21.10.2021 um 20:42 schrieb Michael Biebl:
>> [always CC the bug report email address on replies]
>>
>> Am 21.10.21 um 20:25 schrieb Brown, Thomas:
>>>
>>> On 10/21/21 2:14 PM, Michael Biebl wrote:
>>>> Control: reassign -1 clamav-daemon
>>>>
>>>>
>>>> Not sure why you filed this against the systemd package when the 
>>>> service file in question is shipped by clamav-daemon.
>>>> Reassigning accordingly.
>>>>
>>> This is a systemd problem that occurs when attempting to launch 
>>> clamav-daemon.
>>>
>>> systemd[1]: Condition check resulted in Clam AntiVirus userspace 
>>> daemon being skipped.
>>
>> This condition is specified by the clamav-daemon.service though.
>> I assume this means that the clamav daemon package is not properly 
>> set-up. not an issue of systemd.
>>
>
> Your service fails to start or rather is not started by systemd, as 
> the condition(s) specified in
>
> https://sources.debian.org/src/clamav/0.103.3+dfsg-1/clamd/clamav-daemon.service.in/ 
>
>
>
> # Check for database existence
> ConditionPathExistsGlob=@DBDIR@/main.{c[vl]d,inc}
> ConditionPathExistsGlob=@DBDIR@/daily.{c[vl]d,inc}
>
> is not met.
>
> The log message about StandardOutput=syslog is just a warning but does 
> not make the service fail.
>
Ok, but is there a way to throttle or stagger the condition checks so 
that they only happen once every 5 minutes for example?

This problem seems similar to https://github.com/systemd/systemd/issues/2467

Additionally I should be able to remove StandardOutput from the 
clamav-daemon.service configuration by removing it from the service unit 
definition in /etc/systemd/system/ but it still appears to be present or 
in effect because the Condition check error is still seen in this case 
but not when removed from the service unit definition in 
/lib/systemd/system/.

Finally it would appear that repeated condition check failures are 
resulting in a system reboot in the ConditionPathExistsGlob case.  Is 
there a recommended configuration to prevent this from happening?


-- 
Kind Regards,

Thomas Brown

Linux Developer
EPS PBU RT Solution Services

411 Leggett Drive
Suite 502
Kanata, ON, Canada
K2K 3C9
  
Tel: 613-963-1016
Fax: 613-599-1060