please look at your systemlogs when you mangle around in unit files clamd-0.101.2-2.fc29.x86_64 Jul 1 15:34:23 testserver systemd[1]: /usr/lib/systemd/system/clamd:1: .include directives are deprecated, and support for them will be removed in a future version of systemd. Please use drop-in files instead. Jul 1 15:34:23 testserver systemd[1]: /usr/lib/systemd/system/clamd:1: .include directives are deprecated, and support for them will be removed in a future version of systemd. Please use drop-in files instead. Jul 1 15:34:24 testserver systemd[1]: /usr/lib/systemd/system/clamd:1: .include directives are deprecated, and support for them will be removed in a future version of systemd. Please use drop-in files instead. Jul 1 15:34:24 testserver systemd[1]: /usr/lib/systemd/system/clamd:1: .include directives are deprecated, and support for them will be removed in a future version of systemd. Please use drop-in files instead. Jul 1 15:34:49 testserver systemd[1]: /usr/lib/systemd/system/clamd:1: .include directives are deprecated, and support for them will be removed in a future version of systemd. Please use drop-in files instead. Jul 1 15:34:49 testserver systemd[1]: /usr/lib/systemd/system/clamd:1: .include directives are deprecated, and support for them will be removed in a future version of systemd. Please use drop-in files instead. Jul 1 15:34:49 testserver systemd[1]: /usr/lib/systemd/system/clamd:1: .include directives are deprecated, and support for them will be removed in a future version of systemd. Please use drop-in files instead. Jul 1 15:34:50 testserver systemd[1]: /usr/lib/systemd/system/clamd:1: .include directives are deprecated, and support for them will be removed in a future version of systemd. Please use drop-in files instead.
Thanks for the report, have you any patch or pull request to fix this warning ?
https://coreos.com/os/docs/latest/using-systemd-drop-in-units.html for distibution stuff as usual /usr/lib/systemd/systemd/servicename.d/ i don't use the shipped service at all which makes it even worser is this really needed at all? when someone overwrites the complete unit in /etc/systemd/system he also needs to be ware that the dropins have to be symlinked to /dev/null or you still have a mix of your intended complete override and distro snippets which becomes a nightmare if they are randomly introduced within minor package updates not even raise a upstream version like this
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Pull request here: https://src.fedoraproject.org/rpms/clamav/pull-request/7 constructive comments welcome. This drops the clamd unit and makes use of the clamd@.service instance unit.
Same on F30.
Same problem in CentOS 8 and epel-8 packages clamav-0.101.4-1.el8.x86_64 clamav-filesystem-0.101.4-1.el8.noarch clamav-lib-0.101.4-1.el8.x86_64 clamav-milter-0.101.4-1.el8.x86_64 clamav-update-0.101.4-1.el8.x86_64 clamd-0.101.4-1.el8.x86_64
clamav-0.101.5-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-1543eae191
clamav-0.101.5-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-dcbfe89e39
clamav-0.101.5-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-d6b0a398c2
clamav-0.101.5-1.el8 has been pushed to the Fedora EPEL 8 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-52445f11c2
clamav-0.101.5-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-ce438e7857
clamav-0.101.5-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
clamav-0.101.5-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.
clamav-0.101.5-1.el8 has been pushed to the Fedora EPEL 8 stable repository. If problems still persist, please make note of it in this bug report.
clamav-0.101.5-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.
0.102.1 was already out as that was packaged Dec 22 01:55:16 buildserver freshclam[543633]: Local version: 0.101.5 Recommended version: 0.102.1 Dec 22 01:55:16 buildserver freshclam[543633]: DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav
Did something else change because there isn't a systemd clamd service at all anymore... Install clamav-0.102.2-2.fc31.x86_64 @updates Install clamav-filesystem-0.102.2-2.fc31.noarch @updates Install clamav-lib-0.102.2-2.fc31.x86_64 @updates Install clamav-update-0.102.2-2.fc31.x86_64 @updates sudo systemctl enable --now clamd@scan Failed to enable unit: Unit file clamd does not exist. sudo systemctl start clamd@scan Failed to start clamd: Unit clamd not found. sudo find /usr/lib/systemd/system -iname "clam*" /usr/lib/systemd/system/clamav-freshclam.service How are we suppose to enable / start a clam daemon instanced unit if at least clamd@.service isn't provided? Isn't this what Sergio was asking in this comment? https://src.fedoraproject.org/rpms/clamav/pull-request/7#comment-34049
I think you forgot to install the clamd package. (In reply to mwp.junk from comment #17) > Did something else change because there isn't a systemd clamd service at all > anymore... > > > Install clamav-0.102.2-2.fc31.x86_64 @updates > Install clamav-filesystem-0.102.2-2.fc31.noarch @updates > Install clamav-lib-0.102.2-2.fc31.x86_64 @updates > Install clamav-update-0.102.2-2.fc31.x86_64 @updates >
lol... so I did! thanks.