Type=simple is completly un-trustable because it returns immediatly and the clamav-milter don't work if the clamd service is not available and don't recover which leads in temporary reject all messages by postfix 3 options: * fix the milter so it recovers if clamd is later ready for connections * change clamd to Type=forking * add a ExecStopPost which tests and waits until it is ready for connections for option 3 you may look at the MariaDB/MySQL service see also that bugreprot in conext of clamav https://bugzilla.redhat.com/show_bug.cgi?id=1126595#c1
that happens without type=forking and it is not necessary if Before/After are already ordered correctly Aug 4 23:51:43 testserver clamav-milter[962]: ERROR: Failed to initiate streaming/fdpassing Aug 4 23:51:43 testserver clamav-milter[962]: WARNING: No clamd server appears to be available
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
(In reply to Harald Reindl from comment #0) > Type=simple is completly un-trustable because it returns immediatly and the > clamav-milter don't work if the clamd service is not available and don't > recover which leads in temporary reject all messages by postfix > > 3 options: > > * fix the milter so it recovers if clamd is later ready for connections > * change clamd to Type=forking > * add a ExecStopPost which tests and waits until it is ready for connections > > for option 3 you may look at the MariaDB/MySQL service > > see also that bugreprot in conext of clamav > https://bugzilla.redhat.com/show_bug.cgi?id=1126595#c1 I changed clamd to Type=forking
clamav-0.99.2-15.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-546d6f3abc
clamav-0.99.2-15.fc27 has been pushed to the Fedora 27 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-2018-546d6f3abc
clamav-0.99.2-16.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-546d6f3abc
clamav-0.99.2-16.fc27 has been pushed to the Fedora 27 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-2018-546d6f3abc
clamav-0.99.2-17.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-e5e5ec6ca2
clamav-0.99.2-17.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-1713497ca1
clamav-0.99.2-17.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-2018-1713497ca1
clamav-0.99.2-17.fc27 has been pushed to the Fedora 27 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-2018-e5e5ec6ca2
(In reply to Sergio Monteiro Basto from comment #4) > I changed clamd to Type=forking Seems a regression see [1] [1] https://src.fedoraproject.org/rpms/clamav/c/8e91346cb14057357c325449041edea8df06b1e5?branch=master
who is that idiot and why don't he read the fucking systemd manual? https://www.freedesktop.org/software/systemd/man/systemd.service.html If set to simple (the default if neither Type= nor BusName=, but ExecStart= are specified), it is expected that the process configured with ExecStart= is the main process of the service. In this mode, if the process offers functionality to other processes on the system, its communication channels should be installed before the daemon is started up (e.g. sockets set up by systemd, via socket activation), as systemd will immediately proceed starting follow-up units how does that braindead fool imagine that services which use clamd smell that they have wait to start? and hence i overwride 99% of all unit-files in /etc/systemd/system/ because too many maintainers don't have the slightest clue what they are doing
@Harald I really don't understand why your account aren't suspend yet , the author of commit is there , so don't insult him neither anyone, neither use offensive language , if not I will have to report you . I think is about : https://bodhi.fedoraproject.org/updates/clamav-0.99.2-17.fc27#comment-720009
@Sergio - just because one guy did a override of the originally broken service which now needs to be corrected someone goes out and change the type back without any additional comment in bodhi? frankly for many things i don't care about Fedora packages at all for years because when i override https://bodhi.fedoraproject.org/updates/clamav-0.99.2-17.fc27#comment-720009 can't happen because i cloe the whole unit in /etc/systemd/system or in most cases fork the whole packages because i am tired of such long response times and discussions at all
the "--foreground=yes" is just plain wrong with Type=forking - that's it don't get me wrong but i did expect a maintainer touching something to try if it works at all and then that won't have hapüpended - the proper fix anyways is "Type=forking" and remove "--foreground=yes" from ExecStart and not roll back to Type=simple
that's BTW not clamd specific - "--foreground=yes" or similar called params disable the forking behavior from the daemon at start which is required by Type=simple
I'm fine with going back to Type=forking and removing --foreground=yes, I was just trying to fix it now starting with how it is configured.
it's that simple for every unit out there: Type=simple ExecStart=binary --foreground=yes Type=forking ExecStart=binary --daemonize=yes
/usr/sbin/clamd -c /etc/clamd.d/%i.conf --daemonize=yes /usr/sbin/clamd: unrecognized option `--daemonize=yes' ERROR: Unknown option passed ERROR: Can't parse command line options
Hi, thanks for the testing please can you edit again /usr/lib/systemd/system/clamd@.service and try with [1] and confirm that is working for you after run [2] , It seems that is working for me now. Thanks [1] [Unit] Description = clamd scanner (%i) daemon After = syslog.target nss-lookup.target network.target [Service] Type = forking ExecStart = /usr/sbin/clamd -c /etc/clamd.d/%i.conf Restart = on-failure [2] systemctl daemon-reload systemctl start clamd
That works for me. Presumably we should change clamav-milter.systemd to forking (and drop foreground=yes) for the same reason as well. I've tested that as well as seems to work fine.
OK thanks for testing and my sincere apologies for the bad behavior of Harald. I'm going update package now , more 355 emails of spam o'matic (I'm fixing 9 bugs now)
clamav-0.99.2-18.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-2a1f469c85
clamav-0.99.2-18.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-11ba3bced1
clamav-0.99.2-18.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-2018-11ba3bced1
clamav-0.99.2-18.fc27 has been pushed to the Fedora 27 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-2018-2a1f469c85
clamav-0.99.2-18.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.