On Wed, 2005-06-29 at 09:07 -0700, Dale Anderson wrote:
I just updated my clamav to version 0.86.1/960
I had to change the clamd.conf I was receiving when
tring to start Clamd. StreamSaveToDisk not supported.
So I alter the clamd.conf that came with the update
version and now clamd dies when
I just updated my clamav to version 0.86.1/960
I had to change the clamd.conf I was receiving when
tring to start Clamd. StreamSaveToDisk not supported.
So I alter the clamd.conf that came with the update
version and now clamd dies when I send an zip
attachment through it. It worked on the
I've been trying out the 20050524 devel snapshot on one of my servers since
the post regarding the buffer overrun problem. System is Solaris 8 on
UltraSparc, gcc 3.4.0
The 20050524 clamd is now dieing on database reloads. (I just upgraded to
the 20050526 snap, same behavior)
Enableing debug
Hi List
I have a problem with clamd dying without warning.
Nothing appears in the log files.
Below are the lst entries in the log:
snip
Sun Jul 25 04:20:37 2004 - Reading databases from /usr/local/share/clamav
Sun Jul 25 04:20:47 2004 - Database correctly reloaded (22911 viruses)
Sun Jul 25
* Thomas Kinghorn [EMAIL PROTECTED] [20040726 10:26]: wrote:
Hi List
I have a problem with clamd dying without warning.
Nothing appears in the log files.
Below are the lst entries in the log:
snip
Sun Jul 25 04:20:37 2004 - Reading databases from /usr/local/share/clamav
Sun Jul 25
Thomas Kinghorn wrote:
Hi List
I have a problem with clamd dying without warning.
Nothing appears in the log files.
You need to put a watchdog script in place that runs out of cron. Clamd has
severe memory management problems and will use all you have - your cron script
should look for two
I am running FreeBSD 4.9 w/ sendmail - mimedefang - clamav and spamassasin.
clamd seems to die for no apparent reason.. here is what I had from logs:
From ClamAV debug:
-
LibClamAV debug: Scanning
/var/spool/MIMEDefang/mdefang-i1B7omll041275/Work/msg-39331-137.zip
LibClamAV debug: Starting
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of GVB
Sent: 13 February 2004 19:31
clamd seems to die for no apparent reason.. here is what I
had from logs:
From ClamAV debug:
-
LibClamAV debug: Zip - DMSscan.psd: Size exceeded (13992803,
Are you saying that if clamd hits some sort of configurable limit that the
daemon is just supposed to die?
-gvb
On Fri, 13 Feb 2004, Rob wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of GVB
Sent: 13 February 2004 19:31
clamd seems to
On Fri, 13 Feb 2004 11:30:34 -0800 (PST)
GVB [EMAIL PROTECTED] wrote:
I am running FreeBSD 4.9 w/ sendmail - mimedefang - clamav and
spamassasin.
The problem is in the mimedefang and FreeBSD - mimdefang closes
connection with clamd as soon as first error appears and when clamd
tries to write
Does anyone have a workaround for this issue?
-gvb
On Fri, 13 Feb 2004, Tomasz Kojm wrote:
On Fri, 13 Feb 2004 11:30:34 -0800 (PST)
GVB [EMAIL PROTECTED] wrote:
I am running FreeBSD 4.9 w/ sendmail - mimedefang - clamav and
spamassasin.
The problem is in the mimedefang and FreeBSD -
On Thu, 2 Oct 2003 09:55:04 +0300 Odhiambo Washington [EMAIL PROTECTED] wrote:
Okay, I know this is not good at all, that I run the CVS version of
clamav
on a production box. It's suicide. I've run the daily snapshots for
some
time without disappointment when it comes to supervising the
Odhiambo Washington wrote:
Okay, I know this is not good at all, that I run the CVS version of clamav
on a production box. It's suicide. I've run the daily snapshots for some
time without disappointment when it comes to supervising the service with
daemontools. However, something in CVS seems to
Okay, I know this is not good at all, that I run the CVS version of clamav
on a production box. It's suicide. I've run the daily snapshots for some
time without disappointment when it comes to supervising the service with
daemontools. However, something in CVS seems to completely defy daemontools!
Okay, I know this is not good at all, that I run the CVS version of clamav
on a production box. It's suicide. I've run the daily snapshots for some
time without disappointment when it comes to supervising the service with
daemontools. However, something in CVS seems to completely defy
16, 2003, at 03:54 PM, Lynn Duerksen wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Tomasz Kojm
Sent: Tuesday, September 16, 2003 10:23 AM
To: [EMAIL PROTECTED]
Subject: Re: [Clamav-users] clamd dies
I have not seen anyone with a solution so far
I have not seen anyone with a solution so far for my
Postfix-Spamassassin-Openbsd3.3-Amavisd-new setup. On the latest
version freshclam even bombs now. Run the following script from crontab
Freshclam bombs ? Can't believe ;)
Best regards,
Tomasz Kojm
--
oo. [EMAIL
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Tomasz Kojm
Sent: Tuesday, September 16, 2003 10:23 AM
To: [EMAIL PROTECTED]
Subject: Re: [Clamav-users] clamd dies
I have not seen anyone with a solution so far for my
Postfix-Spamassassin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 11 Sep 2003 7:04 pm, Darek M wrote:
2. clamd dies on me on signal 11 (core dump). Is this a common issue?
If so, is there a fix?
What version of clamav, what operating system (distribution if Linux)?
Regardless of the last
19 matches
Mail list logo
