On Mon, 19 Jul 2004 at 7:38:56 -0500, John Fleming wrote:
> ----- Original Message -----
> From: "John Fleming" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, July 18, 2004 10:14 PM
> Subject: [Clamav-users] Clamdscan Error 2
>
> > ClamAV (clamd) was working fine until I updated Debian unstable today.
> Now
> > I'm getting the following header added to ALL emails:
> >
> > X-Virus-Status: Failed
> > X-Virus-Report: /usr/bin/clamdscan error 2
> >
> > I deleted my clamav log and restarted clamav. The new log starts out as
> > usual, but the first email to come in results in the ERROR lines at the
> > bottom. I don't know what's going on here, i.e. whether this is something
> I
> > should be able to diagnose and treat, or whether there is a problem with
> the
> > Debian package, and I should just wait for it to get fixed. Anyone else
> > seeing this and/or have any ideas? Thanks - John
> >
> > [EMAIL PROTECTED]:/var/log/clamav# cat clamav.log
> > Sun Jul 18 21:57:27 2004 -> +++ Started at Sun Jul 18 21:57:27 2004
> > Sun Jul 18 21:57:27 2004 -> clamd daemon 0.74 (OS: linux-gnu, ARCH: i386,
> > CPU: i386)
[...]
> > Sun Jul 18 21:57:28 2004 -> Self checking every 3600 seconds.
> > Sun Jul 18 22:00:52 2004 -> ERROR: ScanStream: accept timeout.
> > Sun Jul 18 22:02:00 2004 -> ERROR: ScanStream: accept timeout.
> > Sun Jul 18 22:02:27 2004 -> ERROR: ScanStream: accept timeout.
> > Sun Jul 18 22:06:01 2004 -> ERROR: ScanStream: accept timeout.
> > Sun Jul 18 22:06:36 2004 -> ERROR: ScanStream: accept timeout.
> > Sun Jul 18 22:07:10 2004 -> ERROR: ScanStream: accept timeout.
> > [EMAIL PROTECTED]:/var/log/clamav#
I don't know if Debian package of 0.74 already contains the fix for the
following bug or not. Quoting my own message:
--------------------------------------------------------------------
From: Tomasz Papszun <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Subject: [Clamav-users] Broken stream scanning in clamdscan 0.74
Date: Wed, 30 Jun 2004 19:45:57 +0200
It turned out the latest version of ClamAV (0.74) and development
versions since devel-20040622 contain a bug regarding handling of stream
scanning in TCP mode. The bug results in clamdscan hanging when scanning
data on stdin ("clamdscan -"). The bug does _not_ affect scanning files
given to clamdscan directly on command line.
The bug was reported today by Piotr Gackiewicz.
A fix will be available tomorrow in CVS.
-------------------------------------------------------------------------
So... if you, by chance, use TCP scanning mode (which we don't know as
you haven't given us your config nor setup), you may check (maybe in
changelog.Debian.gz) whether the fix has been included.
>
> Only one response on this thread so far. I removed clamav (no --purge) and
> reinstalled. I also deleted the virus databases and reran freshclam to get
> fresh files. Now I get clamd error 127 instead of error 2. I tried to run
> dpk-reconfigure clamav-daemon, but it said: "clamav-daemon is broken or not
> fully installed".
In such cases you may try to --purge it and install from scratch. Of
course first back up your configs etc.
> I guess I have to assume the package is broken, given
> this message and the fact that it broke when I upgraded clamav via apt-get.
> Is there a place to report this besides here? Thanks - John
If reinstalling from scratch still fails, you can report a bug to Debian
Bug Tracking system.
--
Tomasz Papszun SysAdm @ TP S.A. Lodz, Poland | And it's only
[EMAIL PROTECTED] http://www.lodz.tpsa.pl/iso/ | ones and zeros.
[EMAIL PROTECTED] http://www.ClamAV.net/ A GPL virus scanner
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
