Description of problem: Several times a day the freshclam-sleep cron job reports: clamd server '/var/run/clamd.scan/clamd.sock' gave '' response Version-Release number of selected component (if applicable): clamav-milter-systemd-0.97.6-1800.fc18.noarch clamav-milter-0.97.6-1800.fc18.i686 clamav-server-sysvinit-0.97.6-1800.fc18.noarch clamav-server-systemd-0.97.6-1800.fc18.noarch clamav-lib-0.97.6-1800.fc18.i686 clamav-update-0.97.6-1800.fc18.i686 clamav-filesystem-0.97.6-1800.fc18.noarch clamav-scanner-systemd-0.97.6-1800.fc18.noarch clamav-server-0.97.6-1800.fc18.i686 clamav-data-empty-0.97.6-1800.fc18.noarch clamav-scanner-0.97.6-1800.fc18.noarch clamav-0.97.6-1800.fc18.i686 clamav-devel-0.97.6-1800.fc18.i686 How reproducible: Very often. Steps to Reproduce: 1. 2. 3. Actual results: Cron job freshclam-sleep reports: clamd server '/var/run/clamd.scan/clamd.sock' gave '' response Expected results: No such message. Additional info:
I am seeing this, too, and have been for a while. I am now on 0.97.8-1. It started on 1/17/2013 if that helps determine what package version introduced it. Here are the timestamps from the e-mails. It's not several times a day and doesn't seem to have a regular pattern. Thu, 17 Jan 2013 05:02:06 -0600 Fri, 18 Jan 2013 11:02:05 -0600 Sun, 20 Jan 2013 20:02:04 -0600 Mon, 21 Jan 2013 14:02:04 -0600 Thu, 17 Jan 2013 08:02:03 -0600 Wed, 23 Jan 2013 17:02:04 -0600 Fri, 25 Jan 2013 14:02:04 -0600 Sun, 27 Jan 2013 11:02:04 -0600 Tue, 29 Jan 2013 02:02:03 -0600 Tue, 29 Jan 2013 14:02:21 -0600 Tue, 29 Jan 2013 17:02:17 -0600 Wed, 30 Jan 2013 08:02:05 -0600 Thu, 31 Jan 2013 11:02:34 -0600 Thu, 31 Jan 2013 14:02:06 -0600 Sat, 2 Feb 2013 14:02:03 -0600 Thu, 31 Jan 2013 17:02:05 -0600 Wed, 6 Feb 2013 17:02:05 -0600 Fri, 8 Feb 2013 08:02:05 -0600 Fri, 8 Feb 2013 05:02:06 -0600 Tue, 12 Feb 2013 08:02:05 -0600 Tue, 12 Feb 2013 20:02:03 -0600 Thu, 14 Feb 2013 08:08:09 -0600 Thu, 14 Feb 2013 11:06:27 -0600 Thu, 14 Feb 2013 14:13:21 -0600 Thu, 14 Feb 2013 17:02:30 -0600 Thu, 21 Feb 2013 02:02:05 -0600 Thu, 21 Feb 2013 14:02:26 -0600 Sat, 23 Feb 2013 20:02:19 -0600 Mon, 25 Feb 2013 14:02:06 -0600 Tue, 26 Feb 2013 14:02:04 -0600 Sun, 3 Mar 2013 08:02:05 -0600 Thu, 7 Mar 2013 11:02:21 -0600 Tue, 12 Mar 2013 17:02:12 -0500 Thu, 14 Mar 2013 05:02:13 -0500 Fri, 15 Mar 2013 20:07:04 -0500 Sat, 16 Mar 2013 23:02:06 -0500 Mon, 18 Mar 2013 05:02:07 -0500 Thu, 21 Mar 2013 14:02:10 -0500 Fri, 22 Mar 2013 08:02:07 -0500 Fri, 22 Mar 2013 20:02:07 -0500 Sat, 23 Mar 2013 14:02:06 -0500 Tue, 26 Mar 2013 14:02:28 -0500 Wed, 27 Mar 2013 23:02:06 -0500 Fri, 29 Mar 2013 02:02:05 -0500 Sat, 30 Mar 2013 14:02:04 -0500 Sun, 31 Mar 2013 23:02:04 -0500 Tue, 2 Apr 2013 14:02:09 -0500 Tue, 2 Apr 2013 20:02:07 -0500 Wed, 3 Apr 2013 05:02:07 -0500 Wed, 3 Apr 2013 20:02:38 -0500 Thu, 4 Apr 2013 17:02:20 -0500 Sun, 7 Apr 2013 14:02:07 -0500 Sun, 7 Apr 2013 17:02:06 -0500 Sun, 7 Apr 2013 20:02:06 -0500 Mon, 8 Apr 2013 11:02:08 -0500 Mon, 8 Apr 2013 20:02:07 -0500 Wed, 10 Apr 2013 17:02:05 -0500 Thu, 11 Apr 2013 20:02:36 -0500 Fri, 12 Apr 2013 11:02:11 -0500 Fri, 12 Apr 2013 20:02:06 -0500 Fri, 12 Apr 2013 23:02:06 -0500 Sun, 14 Apr 2013 23:02:18 -0500 Mon, 15 Apr 2013 08:02:07 -0500 Tue, 16 Apr 2013 14:02:07 -0500 Tue, 16 Apr 2013 20:02:09 -0500 Wed, 17 Apr 2013 11:02:08 -0500 Wed, 17 Apr 2013 17:03:06 -0500 Thu, 18 Apr 2013 17:02:06 -0500 Fri, 19 Apr 2013 02:02:06 -0500 Fri, 19 Apr 2013 05:02:07 -0500 Fri, 19 Apr 2013 14:02:08 -0500 Fri, 19 Apr 2013 20:02:36 -0500 Sat, 20 Apr 2013 17:02:07 -0500 Sun, 21 Apr 2013 14:02:06 -0500 Wed, 24 Apr 2013 08:02:06 -0500 Wed, 24 Apr 2013 11:02:07 -0500 Thu, 25 Apr 2013 11:02:05 -0500 Thu, 25 Apr 2013 23:02:05 -0500 Thu, 25 Apr 2013 20:02:05 -0500 Fri, 26 Apr 2013 23:02:06 -0500 Tue, 30 Apr 2013 14:02:06 -0500 Mon, 29 Apr 2013 23:02:07 -0500 Thu, 2 May 2013 05:02:09 -0500 Sat, 4 May 2013 14:02:06 -0500 Sat, 4 May 2013 20:02:04 -0500 Sun, 5 May 2013 02:02:05 -0500 Mon, 22 Apr 2013 02:02:06 -0500 Mon, 6 May 2013 11:02:05 -0500 Mon, 6 May 2013 20:02:05 -0500 Tue, 7 May 2013 08:02:06 -0500 Tue, 7 May 2013 02:02:06 -0500 Wed, 8 May 2013 08:02:06 -0500 Fri, 10 May 2013 08:02:14 -0500 Sat, 11 May 2013 08:02:10 -0500 Sat, 11 May 2013 23:02:07 -0500 Sun, 12 May 2013 02:02:06 -0500 Tue, 14 May 2013 17:03:30 -0500 Wed, 15 May 2013 02:02:06 -0500 Thu, 16 May 2013 11:02:13 -0500 Fri, 17 May 2013 20:02:08 -0500 Wed, 22 May 2013 08:02:04 -0500 Sat, 25 May 2013 20:02:04 -0500 Mon, 27 May 2013 23:02:07 -0500
I'm seeing it too. It started when I upgraded from F16 to F18.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.
Don't know if this is relevant, but since bug #787434 was rejected, I've had to create the clamd socket as owner/group defang: [root@mail mail]# ls -ld /var/run/clamd.mimedefang/clamd.sock /var/run/clamd.mimedefang/ drwx--x---. 2 defang defang 80 Feb 25 14:53 /var/run/clamd.mimedefang/ srw-rw----. 1 defang defang 0 Feb 25 14:53 /var/run/clamd.mimedefang/clamd.sock [root@mail mail]# ls -lZd /var/run/clamd.mimedefang/clamd.sock /var/run/clamd.mimedefang/ drwx--x---. defang defang system_u:object_r:antivirus_var_run_t:s0 /var/run/clamd.mimedefang/ srw-rw----. defang defang system_u:object_r:antivirus_var_run_t:s0 /var/run/clamd.mimedefang/clamd.sock [root@mail mail]#
What do you need to make progress on this bug?
I get this same error when clamd is notified of the database update. The database is reloaded but it prints the error. clamav-server-systemd-0.98.1-1.fc20.noarch clamav-lib-0.98.1-1.fc20.x86_64 clamav-update-0.98.1-1.fc20.x86_64 clamav-data-0.98.1-1.fc20.noarch clamav-filesystem-0.98.1-1.fc20.noarch clamav-server-0.98.1-1.fc20.x86_64
After upgrading to amavisd-new-2.8.1-1.fc20.noarch on 2014-03-21, I now see this error, which I hadn't seen before. I can confirm the same as Juan reported in Comment 7.
Since upgrading to Fedora 20 from Fedora 19, I am now seeing this as well: amavisd-new-2.8.1-1.fc20.noarch clamav-0.98.1-1.fc20.x86_64 clamav-data-empty-0.98.1-1.fc20.noarch clamav-filesystem-0.98.1-1.fc20.noarch clamav-lib-0.98.1-1.fc20.x86_64 clamav-server-0.98.1-1.fc20.x86_64 clamav-server-sysvinit-0.98.1-1.fc20.noarch clamav-update-0.98.1-1.fc20.x86_64
Just wondering if there is any progress on this? I'm also experiencing this problem, across many servers, making management of all those cron emails a pain. What is the normal procedure for this? It looks to be ongoing for quite a while - has anyone investigated this yet?
I can confirm this as well. After upgrading to Fedora20 I started to get these too. clamav-scanner-systemd-0.98.1-1.fc20.noarch clamav-filesystem-0.98.1-1.fc20.noarch clamav-scanner-0.98.1-1.fc20.noarch clamav-lib-0.98.1-1.fc20.i686 clamav-milter-0.98.1-1.fc20.i686 clamav-server-systemd-0.98.1-1.fc20.noarch clamav-data-0.98.1-1.fc20.noarch clamav-milter-systemd-0.98.1-1.fc20.noarch clamav-update-0.98.1-1.fc20.i686 clamav-server-0.98.1-1.fc20.i686
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.
*** Bug 1250008 has been marked as a duplicate of this bug. ***
as last complain was in 2015-12-02 and I believe that is fixed , I'm closing as "works for me"