well clamAV instillation outdated is a normal warning and not going to stop databases from updating(unless it is a way outdated version and this is not)
I have to say I’m out of ideas as I never had such a problem with clamAV. I can only think maybe SELinux? was this just a standard download of RHEL 10.2? You will have to check all owner/group relations , I just dont know at this point.
root@srv1:/home/moon# systemctl status clamd@scan.service
× clamd@scan.service - clamd scanner (scan) daemon
Loaded: loaded (/usr/lib/systemd/system/clamd@.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Sat 2026-08-01 22:26:01 IST; 11s ago
Invocation: 29c73f1ba2ce48279df110c85987df21
Docs: man:clamd(8)
man:clamd.conf(5)
Introduction - ClamAV Documentation
Process: 21030 ExecStart=/usr/sbin/clamd -c /etc/clamd.d/scan.conf (code=exited, status=1/FAILURE)
Aug 01 22:26:01 srv1.projectok.com systemd[1]: clamd@scan.service: Scheduled restart job, restart counter is at 5.
Aug 01 22:26:01 srv1.projectok.com systemd[1]: clamd@scan.service: Start request repeated too quickly.
Aug 01 22:26:01 srv1.projectok.com systemd[1]: clamd@scan.service: Failed with result ‘exit-code’.
Aug 01 22:26:01 srv1.projectok.com systemd[1]: Failed to start clamd@scan.service - clamd scanner (scan) daemon.
root@srv1:/home/moon# journalctl -xeu clamd@scan.service
░░ Support: Red Hat Customer Experience & Engagement | Red Hat Customer Portal
░░
░░ An ExecStart= process belonging to unit clamd@scan.service has exited.
░░
░░ The process’ exit code is ‘exited’ and its exit status is 1.
Aug 01 22:26:01 srv1.projectok.com systemd[1]: clamd@scan.service: Failed with result ‘exit-code’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Red Hat Customer Experience & Engagement | Red Hat Customer Portal
░░
░░ The unit clamd@scan.service has entered the ‘failed’ state with result ‘exit-code’.
Aug 01 22:26:01 srv1.projectok.com systemd[1]: Failed to start clamd@scan.service - clamd scanner (scan) daemon.
░░ Subject: A start job for unit clamd@scan.service has failed
░░ Defined-By: systemd
░░ Support: Red Hat Customer Experience & Engagement | Red Hat Customer Portal
░░
░░ A start job for unit clamd@scan.service has finished with a failure.
░░
░░ The job identifier is 16327 and the job result is failed.
Aug 01 22:26:01 srv1.projectok.com systemd[1]: clamd@scan.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: Red Hat Customer Experience & Engagement | Red Hat Customer Portal
░░
░░ Automatic restarting of the unit clamd@scan.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Aug 01 22:26:01 srv1.projectok.com systemd[1]: clamd@scan.service: Start request repeated too quickly.
Aug 01 22:26:01 srv1.projectok.com systemd[1]: clamd@scan.service: Failed with result ‘exit-code’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Red Hat Customer Experience & Engagement | Red Hat Customer Portal
░░
░░ The unit clamd@scan.service has entered the ‘failed’ state with result ‘exit-code’.
Aug 01 22:26:01 srv1.projectok.com systemd[1]: Failed to start clamd@scan.service - clamd scanner (scan) daemon.
░░ Subject: A start job for unit clamd@scan.service has failed
░░ Defined-By: systemd
░░ Support: Red Hat Customer Experience & Engagement | Red Hat Customer Portal
░░
░░ A start job for unit clamd@scan.service has finished with a failure.
░░
░░ The job identifier is 16479 and the job result is failed.
lines 1462-1502/1502 (END)
which os are you using?
Does this help?
As I stated above I’m using Rocky Linux 10.2 and it is 100% 1:1 binary compatible with RHEL
No, not yet. Although, this and the wizard fix are the last issues on my todo list before the upcoming release.
I’m planning to look into it within the next few days.
And, apologies for the delay, as there has been a lot of other Webmin- and Virtualmin-related work involved recently.