Created attachment 1671112 [details] /etc/cron.d/clamav-update patch file Description of problem: /usr/bin/freshclam --quiet returns "Connecting via <proxy.domain.tld>" on stdout after clamav-update-0.102.2-3.el7.x86_64. As a result cron send a mail to root every 3 hours because of /etc/cron.d/clamav-update cron script Version-Release number of selected component (if applicable): Name : clamav-update Arch : x86_64 Version : 0.102.2 Release : 3.el7 Steps to Reproduce: $sudo freshclam --quiet Actual results: "Connecting via <proxy hostname/ip>" string on stdout, where <proxy hostname/ip> is the HTTPProxyServer value into /etc/freshclam.conf file Expected results: Null stdout Additional info: Edit /etc/cron.d/clamav-update adding a stdout redirect to /dev/null to /usr/share/clamav/freshclam-sleep script.
I've added the redirect to freshclam-sleep directly. Linked to upstream bug.
FEDORA-EPEL-2020-c9de701438 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-c9de701438
clamav-0.102.2-4.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-2020-c9de701438
FEDORA-EPEL-2020-c9de701438 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.
I'm looking at clamav-update-0.102.2-4.el7.x86_64 out of EPEL 7 installed today on a server using a proxy for internet access. It does not appear to have the redirect patch applied. I've checked both the package from EPEL and downloaded directly from koji, and removed and reinstalled the clamav-update package with no change. Was there a different solution applied to this issue besides the patch attached above?
I am still seeing this behaviour with 'ClamAV 0.103.0/26092/Fri Feb 26 12:12:59 2021' We use a cronjob of '11,31,51 * * * * /usr/bin/freshclam --quiet' which results in an example with just the line 'Connecting via xx.xx.ac.uk' With the same cronjob this never used to output to stdout. I've been ignoring it for quite a while but it creates quite a lot of useless emails.
https://bugzilla.clamav.net/show_bug.cgi?id=12492 still not fixed ... I think we should silent crontab with patch proposed in this report
FEDORA-2021-b6825699a7 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-b6825699a7
FEDORA-2021-5e3028e5a2 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-5e3028e5a2
FEDORA-2021-ff3c7ea14a has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ff3c7ea14a
FEDORA-EPEL-2021-a847c261f5 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-a847c261f5
FEDORA-EPEL-2021-7265da6992 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-7265da6992
FEDORA-2021-b6825699a7 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-b6825699a7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-b6825699a7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2021-a847c261f5 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-a847c261f5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2021-7265da6992 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-7265da6992 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-5e3028e5a2 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-5e3028e5a2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-5e3028e5a2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-ff3c7ea14a has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-ff3c7ea14a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-ff3c7ea14a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-5e3028e5a2 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-ff3c7ea14a has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-b6825699a7 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2021-a847c261f5 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2021-7265da6992 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.
Hi, This is still happening for me running ClamAV 0.103.2/26197/Thu Jun 10 12:10:09 2021 Just as a reminder of my setup - I have a cron entry with the following - MAILTO=xxx.uk 11 */2 * * * /usr/bin/freshclam --quiet and this is resulting in an email to the MAILTO address containing "Connecting via xx.xxx.ac.uk"
the file /etc/cron.d/clamav-update now have > /dev/null [1] it is the fix on this report , freshclam-sleep also was quieted when used with proxy on commit [2] . I think if you use a custom script you should also add "> /dev/null" [3] [1] 0 */3 * * * root /usr/share/clamav/freshclam-sleep > /dev/null [2] https://src.fedoraproject.org/rpms/clamav/c/c5b54494db0a5cf1f4bc3d2a5519d68d72220694 [3] + /usr/bin/freshclam --quiet > /dev/null
Thanks Sergio, I'd seen that workaround previously but I was hoping it was going to be fixed at the root cause. I don't want to come off sounding hostile but to put it bluntly, this shouldn't be about how 'freshclam --quiet' is run, the flag simply doesn't currently do what it is supposed to do. Using 'freshclam --help' shows the following description '--quiet Only output error messages' If the 'fix' to this is to simply send stdout to /dev/null then the help description should be changed to '--quiet Only output the proxy connection information and error messages' I'll use the suggested workaround going forward. Regards Mickey
https://bugzilla.clamav.net/show_bug.cgi?id=12492 still not fixed, if one day it was fixed, we will revert these workarounds