Hi, all,
running:
ClamAV 0.88.6/2405/Tue Jan 2 09:39:39 2007
on Solaris 9
During the weekend we had problems on two (out of four) mailservers
which run clamav, where freshclam 'died'. i.e. the freshclam process was
gone. We use db.nl.clamav.net (on one mailserver) and db.de.clamav.net
(on
On Tue, Jan 02, 2007 at 01:12:03PM +0100, Rolf E. Sonneveld said:
Hi, all,
running:
ClamAV 0.88.6/2405/Tue Jan 2 09:39:39 2007
on Solaris 9
During the weekend we had problems on two (out of four) mailservers
which run clamav, where freshclam 'died'. i.e. the freshclam process was
On 20/12/06 16:49, Edward Dam wrote:
On 12/13/06, Ian Abbott [EMAIL PROTECTED] wrote:
On 13/12/06 14:28, Edward Dam wrote:
Hi Ian,
Thanks for the help.
I've only got the main.cvd and daily.cvd databases in use right now,
until I
get this sorted out - so it's not a 3rd party db or script
Hi, Stephen,
first of all, thanks for your reply.
Stephen Gran wrote:
On Tue, Jan 02, 2007 at 01:12:03PM +0100, Rolf E. Sonneveld said:
Hi, all,
running:
ClamAV 0.88.6/2405/Tue Jan 2 09:39:39 2007
on Solaris 9
During the weekend we had problems on two (out of four) mailservers
which
I'm running a RH 9 / Plesk server with Clamav version 0.88.7. Freshclam
pulled down the new main.cvd (version 42) on 12/31/2006. Clamd
immediately choked on it and I had to revert to the stock main.cvd
that comes in the package. Subsequent tests have confirmed that the
daily.cvd pulled by
On Tue, Jan 02, 2007 at 10:41:21AM -0500, Ben Wilson said:
I'm running a RH 9 / Plesk server with Clamav version 0.88.7. Freshclam
pulled down the new main.cvd (version 42) on 12/31/2006. Clamd
immediately choked on it and I had to revert to the stock main.cvd
that comes in the package.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Jan 02, 2007 at 10:41:21AM -0500, Ben Wilson wrote:
LibClamAV Error: Cannot close file /tmp/clamav-29cad58e042679e3/main.fp.
cli_untgz: No space left on device
LibClamAV Error: cli_cvdload(): Can't unpack CVD file.
LibClamAV Error: Can't load
On 02/01/07 12:12, Rolf E. Sonneveld wrote:
According to the monitoring system, the freshclam process disappeared
between 14:29 and 14:34. Running ClamAV on Solaris 9. Any idea why after
a 'connection refused' or 'connection timed out' the freshclam process
dies?
It would be nice if there
Out of curiosity, I happened to log in and run freshclam this morning.
On two v0.88.7 installs, I see this:
~$ freshclam -v
Current working dir is /usr/local/share/clamav
Max retries == 3
ClamAV update process started at Tue Jan 2 14:17:48 2007
Querying current.cvd.clamav.net
TTL: 433
Software
Chuck Swiger wrote:
Bill Landry wrote:
[ ... ]
You are preaching to the choir here, as you have no argument from me. I
raised the same issue the last time this happened to me a few weeks ago
and clamd died twice on me in one day. The script work-around to check
the databases before
Ian Abbott wrote:
On 02/01/07 12:12, Rolf E. Sonneveld wrote:
According to the monitoring system, the freshclam process disappeared
between 14:29 and 14:34. Running ClamAV on Solaris 9. Any idea why
after a 'connection refused' or 'connection timed out' the freshclam
process dies?
It would
11 matches
Mail list logo
