Topic: freshclam: Update failed

[rgmhtt]

Admin got an email:

Code: [Select]

2009-03-27 04:04:50.049486500 ClamAV update process started at Fri Mar 27 04:04:50 2009
2009-03-27 04:04:50.050920500 WARNING: Your ClamAV installation is OUTDATED!
2009-03-27 04:04:50.050926500 WARNING: Local version: 0.94.2 Recommended version: 0.95
2009-03-27 04:04:50.050931500 DON'T PANIC! Read http://www.clamav.net/support/faq
2009-03-27 04:04:50.072525500 main.cld is up to date (version: 50, sigs: 500667, f-level: 38, builder: sven)
2009-03-27 04:05:21.573366500 nonblock_connect: connect timing out (30 secs)
2009-03-27 04:05:21.573375500 Can't connect to port 80 of host database.clamav.net (IP: 199.184.215.2)
2009-03-27 04:05:21.573380500 Trying host database.clamav.net (208.72.56.53)...
2009-03-27 04:05:21.682188500 WARNING: getfile: daily-9172.cdiff not found on remote server (IP: 208.72.56.53)
2009-03-27 04:05:21.682196500 WARNING: getpatch: Can't download daily-9172.cdiff from database.clamav.net
2009-03-27 04:05:51.683639500 nonblock_connect: connect timing out (30 secs)
2009-03-27 04:05:51.683648500 Can't connect to port 80 of host database.clamav.net (IP: 199.184.215.2)
2009-03-27 04:05:51.683654500 Trying host database.clamav.net (208.72.56.53)...
2009-03-27 04:05:51.790442500 WARNING: getfile: daily-9172.cdiff not found on remote server (IP: 208.72.56.53)
2009-03-27 04:05:51.790451500 WARNING: getpatch: Can't download daily-9172.cdiff from database.clamav.net
2009-03-27 04:06:21.791938500 nonblock_connect: connect timing out (30 secs)
2009-03-27 04:06:21.791946500 Can't connect to port 80 of host database.clamav.net (IP: 199.184.215.2)
2009-03-27 04:06:21.791952500 Trying host database.clamav.net (208.72.56.53)...
2009-03-27 04:06:21.898911500 WARNING: getfile: daily-9172.cdiff not found on remote server (IP: 208.72.56.53)
2009-03-27 04:06:21.898920500 WARNING: getpatch: Can't download daily-9172.cdiff from database.clamav.net
2009-03-27 04:06:49.055799500 WARNING: getfile: daily-9172.cdiff not found on remote server (IP: 199.184.215.2)
2009-03-27 04:06:49.055809500 WARNING: getpatch: Can't download daily-9172.cdiff from database.clamav.net
2009-03-27 04:07:15.050805500 WARNING: getfile: daily-9172.cdiff not found on remote server (IP: 199.184.215.2)
2009-03-27 04:07:15.050815500 WARNING: getpatch: Can't download daily-9172.cdiff from database.clamav.net
2009-03-27 04:07:36.047924500 WARNING: getfile: daily-9172.cdiff not found on remote server (IP: 199.184.215.2)
2009-03-27 04:07:36.047934500 ERROR: getpatch: Can't download daily-9172.cdiff from database.clamav.net
2009-03-27 04:07:36.053367500 WARNING: Incremental update failed, trying to download daily.cvd
2009-03-27 04:08:07.168511500 nonblock_connect: connect timing out (30 secs)
2009-03-27 04:08:07.168519500 Can't connect to port 80 of host database.clamav.net (IP: 199.184.215.2)
2009-03-27 04:08:07.168525500 Trying host database.clamav.net (208.72.56.53)...
2009-03-27 04:08:12.358517500 WARNING: Mirror 208.72.56.53 is not synchronized.
2009-03-27 04:08:12.360562500 Giving up on database.clamav.net...
2009-03-27 04:08:12.360697500 Update failed. Your network may be down or none of the mirrors listed in /etc/freshclam.conf is working. Check http://www.clamav.net/support/mirror-problem for possible reasons.

What port is it trying on?  I may have it blocked on my firewall.

Or was something down this morning?  How often does clamav call home for updates?

I only built this server a week ago.

[rgmhtt]

And the next email (the daily cron) had in it:

/etc/cron.daily/freshclam:

ERROR: Verification: MD5 verification error

[Knuddi]

The initial warning is due to "outdated" clam installation even though 0.95 only was release a few days ago. You can fix that issue following this:

http://forums.contribs.org/index.php/topic,43674.0.html

[CharlieBrady]

Admin got an email:

Don't report problems here - Please report bugs and potential bugs in the bug tracker

[rgmhtt]

Don't report problems here - Please report bugs and potential bugs in the bug tracker

But is it a problem with SME, or do I simply have a firewall not configured to support a protocol needed by SME?

I did a bit of digging on clamav, and it seems it is using port 80 which seems to be open.  Is there something else that in a non-expert firewall would have been open outbound?  Was it something that was really happening out in clam-world and I am new to clam and missed the complaining there that something was down (like I see on the Fedora list from time to time)?

So I did not know if I had a reportable problem worthy of a bug report.

But here is where 'culture' comes in.  It seems that this community is more oriented to problems being treated as bug reports.  I can work with that.  It is not what I am use to in so many other areas, but this is your sandbox and I will play by your rules.

[uniqsys]

Or was something down this morning?

I got a similar email error last night on clamav updates too.  Every once in a while this error/email happens. Usually it is something out on the net that causes this. I usually ignore it unless it happens 2 days in a row.  Maybe that is not good, but one can waste a lot of time running after every one of these.  Especially when you know your connectivity is good.  Nothing fancy is being done by freshclam calling home for updates.

How often does clamav call home for updates?  I only built this server a week ago.

I don't know but I think it is at least a daily cron.

RE:

I will play by your rules.

The intent of the bug tracker is to track "issues" that may be potential bugs, in addition to real bugs.  Bugzilla offers a much better format to track and treat problems, even if they are not "real bugs".  It helps EVERYONE and no judgment is implied or taken on you or SME when you use that format.

[rgmhtt]

I got a similar email error last night on clamav updates too.  Every once in a while this error/email happens. Usually it is something out on the net that causes this. I usually ignore it unless it happens 2 days in a row.  Maybe that is not good, but one can waste a lot of time running after every one of these.  Especially when you know your connectivity is good.  Nothing fancy is being done by freshclam calling home for updates.

IMHO this is an example of community experience helping out a newbie.  I am new to clamav.  spamassasin and I are old sparing 'partners', but I never used clamav before.  So I get the input from someone that knows what to expect.

Thanks for the insight uniqsys.

I don't know but I think it is at least a daily cron.

Yeah, I located the cron after a bit of remembering how to do that.

RE: The intent of the bug tracker is to track "issues" that may be potential bugs, in addition to real bugs.  Bugzilla offers a much better format to track and treat problems, even if they are not "real bugs".  It helps EVERYONE and no judgment is implied or taken on you or SME when you use that format.

A bit broader usage than I see elsewhere, but it might be to community size.  Fedora would not want every issue people think they have filed on their bugtrak (when it maybe belongs on someone else bugtrack).

I think I got it.

[wellsi]

This was filed as Bug 5100, and the update has been released
http://forums.contribs.org/index.php/topic,43495.msg208654.html#msg208654

At least the following part is resolved by the latest update to ClamAV that allows updates to proceed again.
2009-03-27 04:04:50.050920500 WARNING: Your ClamAV installation is OUTDATED!
2009-03-27 04:04:50.050926500 WARNING: Local version: 0.94.2 Recommended version: 0.95

[jokiin]

But is it a problem with SME,

In my experience I've seen this many times over the years when a new version is released and it takes the team a few days to get the updates sorted and roll them out, I can't ever remember it taking more than a few days to get sorted though, these days I don't worry too much when I see a message like this as I know the cavalry is coming and the update is imminent