Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1814698 - freshclam --quiet returns proxy on stdout
Summary: freshclam --quiet returns proxy on stdout
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: clamav
Version: epel7
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL: https://bugzilla.clamav.net/show_bug....
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-18 14:30 UTC by Tasslehoff
Modified: 2021-06-16 10:10 UTC (History)
13 users (show)

Fixed In Version: clamav-0.102.2-4.el7 clamav-0.103.1-3.fc33 clamav-0.103.1-3.fc32 clamav-0.103.1-3.fc34 clamav-0.103.1-3.el8 clamav-0.103.1-3.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-17 02:17:10 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
/etc/cron.d/clamav-update patch file (365 bytes, patch)
2020-03-18 14:30 UTC, Tasslehoff 		no flags Details | Diff
View All

Description Tasslehoff 2020-03-18 14:30:42 UTC 
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.
Comment 1 Orion Poplawski 2020-03-19 01:07:29 UTC 
I've added the redirect to freshclam-sleep directly.  Linked to upstream bug.
Comment 2 Fedora Update System 2020-03-19 01:27:40 UTC 
FEDORA-EPEL-2020-c9de701438 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-c9de701438
Comment 3 Fedora Update System 2020-03-20 02:14:19 UTC 
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
Comment 4 Fedora Update System 2020-04-04 00:43:52 UTC 
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.
Comment 5 Robert Cooper 2020-04-06 20:48:33 UTC 
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?
Comment 6 Mickey 2021-02-26 18:38:45 UTC 
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.
Comment 7 Sergio Basto 2021-02-26 23:06:09 UTC 
https://bugzilla.clamav.net/show_bug.cgi?id=12492 still not fixed ... I think we should silent crontab with patch proposed in this report
Comment 8 Fedora Update System 2021-03-07 23:57:20 UTC 
FEDORA-2021-b6825699a7 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-b6825699a7
Comment 9 Fedora Update System 2021-03-07 23:57:40 UTC 
FEDORA-2021-5e3028e5a2 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-5e3028e5a2
Comment 10 Fedora Update System 2021-03-07 23:57:57 UTC 
FEDORA-2021-ff3c7ea14a has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ff3c7ea14a
Comment 11 Fedora Update System 2021-03-07 23:58:12 UTC 
FEDORA-EPEL-2021-a847c261f5 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-a847c261f5
Comment 12 Fedora Update System 2021-03-07 23:58:31 UTC 
FEDORA-EPEL-2021-7265da6992 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-7265da6992
Comment 13 Fedora Update System 2021-03-08 15:59:42 UTC 
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.
Comment 14 Fedora Update System 2021-03-08 20:31:48 UTC 
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.
Comment 15 Fedora Update System 2021-03-08 20:42:43 UTC 
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.
Comment 16 Fedora Update System 2021-03-08 21:15:33 UTC 
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.
Comment 17 Fedora Update System 2021-03-08 21:27:29 UTC 
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.
Comment 18 Fedora Update System 2021-03-17 02:17:10 UTC 
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.
Comment 19 Fedora Update System 2021-03-17 02:37:53 UTC 
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.
Comment 20 Fedora Update System 2021-03-19 20:08:39 UTC 
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.
Comment 21 Fedora Update System 2021-03-23 01:52:39 UTC 
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.
Comment 22 Fedora Update System 2021-03-23 02:15:45 UTC 
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.
Comment 23 Mickey 2021-06-11 15:28:04 UTC 
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"
Comment 24 Sergio Basto 2021-06-15 22:51:58 UTC 
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
Comment 25 Mickey 2021-06-16 09:33:20 UTC 
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
Comment 26 Sergio Basto 2021-06-16 10:10:33 UTC 
https://bugzilla.clamav.net/show_bug.cgi?id=12492 still not fixed, if one day it was fixed, we will revert these workarounds
Note You need to log in before you can comment on or make changes to this bug.