After reboot or systemctl restart clamd.conf it starts briefly but enters failed state after a timeout. After the systemctl restart times out systemctl status says: clamd.service - Clam AntiVirus Daemon is a TCP/IP or unix domain Loaded: loaded (/usr/lib/systemd/system/clamd.service; enabled; vendor preset: enabled) Active: failed (Result: timeout) Process: 1447 ExecStart=/usr/sbin/clamd --config-file=/etc/clamd.conf (code=killed, signal=TERM) systemd[1]: Starting Clam AntiVirus Daemon is a TCP/IP or unix domain... systemd[1]: clamd.service: Start operation timed out. Terminating. systemd[1]: Failed to start Clam AntiVirus Daemon is a TCP/IP or unix domain. systemd[1]: clamd.service: Unit entered failed state. systemd[1]: clamd.service: Failed with result 'timeout'. Looking at the process list during systemctl start is not yet timed out I see: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1923 0.0 0.0 21652 2444 pts/0 S+ 12:06 0:00 | systemctl start clamd.service root 1924 0.0 0.0 8544 1532 pts/0 S+ 12:06 0:00 | \_ /usr/bin/systemd-tty-ask-password-agent --watch clamav 1925 100 12.6 452812 388372 ? Rs 12:06 0:34 /usr/sbin/clamd --config-file=/etc/clamd.conf In clamav.log I see when failed: Fri Aug 16 12:06:09 2019 -> +++ Started at Fri Aug 16 12:06:09 2019 Fri Aug 16 12:06:09 2019 -> Received 0 file descriptor(s) from systemd. Fri Aug 16 12:06:09 2019 -> clamd daemon 0.100.3 (OS: linux-gnu, ARCH: x86_64, CPU: x86_64) Fri Aug 16 12:06:09 2019 -> Log file size limited to 2097152 bytes. Fri Aug 16 12:06:09 2019 -> Reading databases from /var/lib/clamav Fri Aug 16 12:06:09 2019 -> Not loading PUA signatures. Fri Aug 16 12:06:09 2019 -> Bytecode: Security mode set to "TrustSigned". When starting manually: Fri Aug 16 12:13:13 2019 -> Not loading PUA signatures. Fri Aug 16 12:13:13 2019 -> Bytecode: Security mode set to "TrustSigned". Fri Aug 16 12:15:11 2019 -> Loaded 6280332 signatures. [...] Fri Aug 16 12:15:13 2019 -> Listening daemon: PID: 2119 So it takes about 2 minutes to load signatures and start, is the timeout in the systemd unit sufficient for that? It also complains on freshclam updates that version is outdated so some signatures may not work so maybe package sould also be updated to latest clamav release.
Thank you Zoltan for all the well judged information you provided. Assigning globally as there is no registered maintainer; CC'ing ThomasS as he has seen this often in the rather distant past (sorry if this is not appropriate).
CC: (none) => thomasAssignee: bugsquad => pkg-bugs
To fix this locally I've added TimeoutStartSec=180 to the [Service] section of /usr/lib/systemd/system/clamd.service I'm not sure about the best value for timeout though as it could take longer on a slower or more busy machine. Maybe something like 5 minutes should be enough even if later updates increase startup time but I let you judge this.
Thomas passed away. It looks like Nicolas has been the de-facto maintainer.
CC: thomas => nicolas.salguero
I feel bad about the gaff. Thanks for putting it right.
Mageia 6 is EOL.
Status: NEW => RESOLVEDResolution: (none) => OLD
(In reply to Nicolas Salguero from comment #5) > Mageia 6 is EOL. Is this issue fixed in mga7 and Cauldron?
CC: (none) => geiger.david68210
Yes, I forgot to say that, in my tests, I cannot reproduce the problem in mga7 for instance.