[clamav-users] ClamAV & Fedora 37 - Long Initialization Time at Boot

Sun Feb 19 00:48:37 UTC 2023

On 2/14/23 14:15, Tim Carr via clamav-users wrote:
> Hello, all. Running a recently-upgraded Fedora 37 server image, and I’ve 
> noticed that the clamd at scan.service is taking about a minute to get 
> running after a reboot. My boot times before were less than a minute, 
> but now that service is really struggling (by eventually succeeds) to 
> get started.
> The systemd-analyze critical-chain command gives me this:
> 
> |multi-user.target @1min 17.914s └─clamd at scan.service @20.838s +57.075s 
> └─nss-lookup.target @20.826s └─named.service @17.367s +3.456s 
> └─network.target @17.284s └─NetworkManager.service @16.337s +945ms 
> └─network-pre.target @16.325s └─firewalld.service @12.114s +4.206s 
> └─polkit.service @18.836s +1.207s └─basic.target @11.876s 
> └─dbus-broker.service @11.115s +756ms └─dbus.socket @11.048s 
> └─sysinit.target @11.020s └─systemd-resolved.service @10.499s +520ms 
> └─systemd-tmpfiles-setup.service @10.123s +354ms └─local-fs.target 
> @10.010s └─run-snapd-ns-tautulli.mnt.mount @32.737s └─run-snapd-ns.mount 
> @32.106s └─local-fs-pre.target @8.406s └─lvm2-monitor.service @4.955s 
> +3.449s └─dm-event.socket @4.899s └─system.slice └─-.slice |
> 
> So, while I get that networking is taking about 21 seconds to be 
> available, I’m not sure why just upgrading to F37 would have changed 
> what’s happening there. I’ve not changed anything about my ClamAV 
> configuration from before the upgrade. Has anyone else run into this, or 
> any other thoughts?
> 
> These are the packages I’m currently running:
> 
> |clamav.x86_64 0.103.7-3.fc37 @updates clamav-data.noarch 0.103.7-3.fc37 
> @updates clamav-filesystem.noarch 0.103.7-3.fc37 @updates 
> clamav-lib.x86_64 0.103.7-3.fc37 @updates clamav-update.x86_64 
> 0.103.7-3.fc37 @updates clamd.x86_64 0.103.7-3.fc37 @updates|

Is this consistently reproducible?  FWIW I just updated my F36 test VM 
to F37 and for me the startup time dropped slightly:

F36:
multi-user.target @25.589s
└─clamd at scan.service @3.427s +22.161s

F37:
multi-user.target @23.807s
└─clamd at scan.service @3.180s +20.625s

If you look at the logs perhaps you can see what step is taking longer?

journalctl -u clamd at scan

Feb 18 17:40:31 f37 systemd[1]: Starting clamd at scan.service - clamd 
scanner (scan) daemon...
Feb 18 17:40:31 f37 clamd[741]: Received 0 file descriptor(s) from systemd.
Feb 18 17:40:31 f37 clamd[741]: clamd daemon 0.103.7 (OS: linux-gnu, 
ARCH: x86_64, CPU: x86_64)
Feb 18 17:40:31 f37 clamd[741]: Log file size limited to 1048576 bytes.
Feb 18 17:40:31 f37 clamd[741]: Reading databases from /var/lib/clamav
Feb 18 17:40:31 f37 clamd[741]: Not loading PUA signatures.
Feb 18 17:40:31 f37 clamd[741]: Bytecode: Security mode set to 
"TrustSigned".
Feb 18 17:40:48 f37 clamd[741]: Loaded 8653122 signatures.
Feb 18 17:40:51 f37 clamd[741]: LOCAL: Unix socket file 
/run/clamd.scan/clamd.sock
Feb 18 17:40:51 f37 clamd[741]: LOCAL: Setting connection queue length 
to 200
Feb 18 17:40:51 f37 clamd[741]: Limits: Global time limit set to 120000 
milliseconds.
Feb 18 17:40:51 f37 clamd[741]: Limits: Global size limit set to 
104857600 bytes.
Feb 18 17:40:51 f37 clamd[741]: Limits: File size limit set to 26214400 
bytes.
Feb 18 17:40:51 f37 clamd[741]: Limits: Recursion level limit set to 17.
Feb 18 17:40:51 f37 clamd[741]: Limits: Files limit set to 10000.
Feb 18 17:40:51 f37 clamd[741]: Limits: MaxEmbeddedPE limit set to 
10485760 bytes.
Feb 18 17:40:51 f37 clamd[741]: Limits: MaxHTMLNormalize limit set to 
10485760 bytes.
Feb 18 17:40:51 f37 clamd[741]: Limits: MaxHTMLNoTags limit set to 
2097152 bytes.
Feb 18 17:40:51 f37 clamd[741]: Limits: MaxScriptNormalize limit set to 
5242880 bytes.
Feb 18 17:40:51 f37 clamd[741]: Limits: MaxZipTypeRcg limit set to 
1048576 bytes.
Feb 18 17:40:51 f37 clamd[741]: Limits: MaxPartitions limit set to 50.
Feb 18 17:40:51 f37 clamd[741]: Limits: MaxIconsPE limit set to 100.
Feb 18 17:40:51 f37 clamd[741]: Limits: MaxRecHWP3 limit set to 16.
Feb 18 17:40:51 f37 clamd[741]: Limits: PCREMatchLimit limit set to 100000.
Feb 18 17:40:51 f37 clamd[741]: Limits: PCRERecMatchLimit limit set to 2000.
Feb 18 17:40:51 f37 clamd[741]: Limits: PCREMaxFileSize limit set to 
26214400.
Feb 18 17:40:51 f37 clamd[741]: Archive support enabled.
Feb 18 17:40:51 f37 clamd[741]: AlertExceedsMax heuristic detection 
disabled.
Feb 18 17:40:51 f37 clamd[741]: Heuristic alerts enabled.
Feb 18 17:40:51 f37 clamd[741]: Portable Executable support enabled.
Feb 18 17:40:51 f37 clamd[741]: ELF support enabled.
Feb 18 17:40:51 f37 clamd[741]: Mail files support enabled.
Feb 18 17:40:51 f37 clamd[741]: OLE2 support enabled.
Feb 18 17:40:51 f37 clamd[741]: PDF support enabled.
Feb 18 17:40:51 f37 clamd[741]: SWF support enabled.
Feb 18 17:40:51 f37 clamd[741]: HTML support enabled.
Feb 18 17:40:51 f37 clamd[741]: XMLDOCS support enabled.
Feb 18 17:40:51 f37 clamd[741]: HWP3 support enabled.
Feb 18 17:40:51 f37 clamd[741]: Self checking every 600 seconds.
Feb 18 17:40:51 f37 systemd[1]: Started clamd at scan.service - clamd 
scanner (scan) daemon.

-- 
Orion Poplawski
he/him/his  - surely the least important thing about me
IT Systems Manager                         720-772-5637
NWRA, Boulder/CoRA Office             FAX: 303-415-9702
3380 Mitchell Lane                       orion at nwra.com
Boulder, CO 80301                 https://www.nwra.com/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3847 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://lists.clamav.net/pipermail/clamav-users/attachments/20230218/58132eae/attachment.p7s>