Bug#467298: updating etch -> volatile helps

[martin f krafft]

also sprach Fabian Ruff <[EMAIL PROTECTED]> [2008.04.07.0049 +0200]:
> I think that updating to volatile doesn't really fixes the problem:
>
> I've experienced the same problems as mentioned above and updated to
> volatile about 3-4 weeks ago:
>
> ~# apt-show-versions |grep clamav
> clamav-base/etch uptodate 0.92.1~dfsg-1volatile1
> clamav-daemon/etch uptodate 0.92.1~dfsg-1volatile1
> clamav-freshclam/etch uptodate 0.92.1~dfsg-1volatile1
> libclamav2/etch uptodate 0.91.2-1~volatile1
> clamav/etch uptodate 0.92.1~dfsg-1volatile1
> libclamav3/etch uptodate 0.92.1~dfsg-1volatile1
>
> This worked fine until 30 minutes ago when clamav went down again with
> apparently the same problem.

I experienced the problem last night with the volatile packages:
freshclam went berserk and took -milter and -daemon with it. I had
to kill freshclam before I could start the other two due to
a database lock. From the logs, it seems that this is due to failure
by freshclam to connect to the mirrors.

-- 
 .''`.   martin f. krafft <[EMAIL PROTECTED]>
: :'  :  proud Debian developer, author, administrator, and user
`. `'`   http://people.debian.org/~madduck - http://debiansystem.info
  `-  Debian - when you have better things to do than fixing systems
 
will kill for oil!


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)

Bug#467298: updating etch -> volatile helps

[Fabian Ruff]

Hello,

I think that updating to volatile doesn't really fixes the problem:

I've experienced the same problems as mentioned above and updated to
volatile about 3-4 weeks ago:

~# apt-show-versions |grep clamav
clamav-base/etch uptodate 0.92.1~dfsg-1volatile1
clamav-daemon/etch uptodate 0.92.1~dfsg-1volatile1
clamav-freshclam/etch uptodate 0.92.1~dfsg-1volatile1
libclamav2/etch uptodate 0.91.2-1~volatile1
clamav/etch uptodate 0.92.1~dfsg-1volatile1
libclamav3/etch uptodate 0.92.1~dfsg-1volatile1

This worked fine until 30 minutes ago when clamav went down again with
apparently the same problem.

Greetings
Fabian

==/var/log/clamav/freshclam.log

Received signal: wake up
ClamAV update process started at Sun Apr  6 23:53:48 2008
main.inc is up to date (version: 46, sigs: 231834, f-level: 26, builder: sven)
nonblock_connect: connect timing out (30 secs)
Can't connect to port 80 of host db.local.clamav.net (IP: 62.26.160.3)
Trying host db.local.clamav.net (212.1.60.18)...
nonblock_connect: connect timing out (30 secs)
Can't connect to port 80 of host db.local.clamav.net (IP: 212.1.60.18)
Trying host db.local.clamav.net (88.198.17.100)...
nonblock_connect: connect timing out (30 secs)
Can't connect to port 80 of host db.local.clamav.net (IP: 88.198.17.100)
Trying host db.local.clamav.net (213.209.100.191)...
nonblock_connect: connect timing out (30 secs)
Can't connect to port 80 of host db.local.clamav.net (IP: 213.209.100.191)
Trying host db.local.clamav.net (89.149.194.18)...
ERROR: getfile: Unknown response from remote server (IP: 89.149.194.18)
ERROR: getpatch: Can't download daily-6636.cdiff from db.local.clamav.net
nonblock_connect: connect timing out (30 secs)
Can't connect to port 80 of host db.local.clamav.net (IP: 195.246.234.199)
Trying host db.local.clamav.net (89.149.194.18)...
ERROR: getfile: Unknown response from remote server (IP: 89.149.194.18)
ERROR: getpatch: Can't download daily-6636.cdiff from db.local.clamav.net
nonblock_connect: connect timing out (30 secs)
Can't connect to port 80 of host db.local.clamav.net (IP: 88.198.17.100)
Trying host db.local.clamav.net (213.209.100.191)...
nonblock_connect: connect timing out (30 secs)
Can't connect to port 80 of host db.local.clamav.net (IP: 213.209.100.191)
Trying host db.local.clamav.net (85.10.242.82)...
nonblock_connect: connect timing out (30 secs)
Can't connect to port 80 of host db.local.clamav.net (IP: 85.10.242.82)
Trying host db.local.clamav.net (91.198.238.33)...
nonblock_connect: connect timing out (30 secs)
Can't connect to port 80 of host db.local.clamav.net (IP: 91.198.238.33)
Ignoring mirror 85.214.44.186 (due to previous errors)
Trying host db.local.clamav.net (89.149.194.18)...
ERROR: getfile: Unknown response from remote server (IP: 89.149.194.18)
ERROR: getpatch: Can't download daily-6636.cdiff from db.local.clamav.net
nonblock_connect: connect timing out (30 secs)
Can't connect to port 80 of host db.local.clamav.net (IP: 91.198.238.33)
Trying host db.local.clamav.net (89.149.194.18)...
ERROR: getfile: Unknown response from remote server (IP: 89.149.194.18)
ERROR: getpatch: Can't download daily-6636.cdiff from db.local.clamav.net
nonblock_connect: connect timing out (30 secs)
Can't connect to port 80 of host db.local.clamav.net (IP: 85.199.169.78)
Ignoring mirror 85.214.44.186 (due to previous errors)


[...] (And a lot more of these lines)

 /var/log/clamav/clamav.log=

Mon Apr  7 00:08:21 2008 -> SelfCheck: Database modification detected. Forcing 
reload.
Mon Apr  7 00:08:21 2008 -> Reading databases from /var/lib/clamav
Mon Apr  7 00:10:31 2008 -> ERROR: reload db failed: Unable to lock database 
directory (try 1)
Mon Apr  7 00:12:41 2008 -> ERROR: reload db failed: Unable to lock database 
directory (try 2)
Mon Apr  7 00:14:51 2008 -> ERROR: reload db failed: Unable to lock database 
directory (try 3)
Mon Apr  7 00:14:51 2008 -> ERROR: reload db failed: Unable to lock database 
directory
Mon Apr  7 00:14:51 2008 -> Terminating because of a fatal error.
Mon Apr  7 00:14:51 2008 -> Socket file removed.
Mon Apr  7 00:14:51 2008 -> Pid file removed.
Mon Apr  7 00:14:51 2008 -> --- Stopped at Mon Apr  7 00:14:51 2008






--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#467298: updating etch -> volatile helps

[Kevin Price]

Hi,

Florian Schlichting schrieb:
> I just updated to volatile (0.92.1...), and all remaining updates were
> downloaded like a breeze!

I experienced exactly the same.

> I think this suggests Stephen was right in
> suspecting the mirrors shut out old connections from old clients...

Ack. I think switching to a version that has better access to the mirror
net is a reaonable workaround. Sure there are enough reasons to switch
to volatile.

Still the old version in etch should not have the effect of freshclam
killing clamav due to bad connectivity to the mirror net. This is the
actual bug that existed for long but only happened to show up recently.
IMHO, it would be a good idea to port the actual bugfix Mathieu
mentioned back into stable, so that clamav will not die, regardless how
bad freshclam reaches any mirrors.

jm2¢

Kevin



signature.asc
Description: OpenPGP digital signature

Bug#467298: updating etch -> volatile helps

[Florian Schlichting]

Hi,

we've had problems very similar to those described above, with freshclam
basically unable to download updates from anywhere, and clamd eventually
dying because of this.

I just updated to volatile (0.92.1...), and all remaining updates were
downloaded like a breeze! I think this suggests Stephen was right in
suspecting the mirrors shut out old connections from old clients...

Florian



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]