On Fri, 2005-09-23 at 09:52 -0500, R. Steven Rainwater wrote:
But I guess the big question now is how can determine for sure if it's a
specifically formatted email that's causing the clamav crashes and, if
so, how can I capture one of the emails?
What platform are you using?
-trog
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of R. Steven
Rainwater
Sent: 27 September 2005 01:02 AM
To: clamav-users@lists.clamav.net
Subject: Re: [Clamav-users] clamav-milter seems unstable with 0.87
On Fri, 2005-09-23 at 22:58, N Fung wrote:
--- [EMAIL
Mark wanted us to know:
... The result is processes that hang forever
on our system. We have a cronjob that does a
killall -HUP sendmail every 2 hours.
that clears out those hanging processes.
That seems a bit crude. :) I wrote a cronjob like that, in Perl; but,
based on 'ps' output, it only
On Mon, Sep 26, 2005 at 09:47:45AM -0700, Todd Lyons wrote:
But with this blanket kill, you also kill connections that may have just
been there for a few seconds, and are still very much alive.
Unfortunately it's required to get sendmail to reload the w class.
You only need to restart the
On Thu, 22 Sep 2005, R. Steven Rainwater wrote:
If anyone has any clues or suggestions, I've love to hear them.
I'm not convinced that your -T=0 is valid syntax. It should be -T0 or
--timeout=0. Using an = with a single-character argument is bad form.
You should be running clmilter_watch
On Mon, 2005-09-26 at 17:46, Damian Menscher wrote:
I'm not convinced that your -T=0 is valid syntax. It
should be -T0 or --timeout=0.
I've switched to using --timeout=0 but it didn't help with the
clamav-milter crashes, which are my main problem.
You should be running clmilter_watch [1]
On Fri, 2005-09-23 at 22:58, N Fung wrote:
--- [EMAIL PROTECTED] wrote:
I think that certain emails are crashing clamav-milter
or clamd when it reads them, causing the processes to
hang. I've noticed that each time we get one of the
errors in the log, an additional clamav-milter process
On Thu, 2005-09-22 at 17:16, Todd Lyons wrote:
R. Steven Rainwater wanted us to know:
Have you tried running clamd and using --external on clamav-milter?
Just tried it. Already had two more crashes in less than 10 minutes!
:-( Both were of the write(A) return -1, expected 5: Broken pipe
On Fri, 23 Sep 2005 09:52:37 -0500 in
[EMAIL PROTECTED] R. Steven Rainwater
[EMAIL PROTECTED] wrote:
I still find it odd that 0.87 seems so broken. All the previous
versions we've run on this machine have been very stable. And I take
it this is not a problem anyone else is seeing, making it
R. Steven Rainwater wrote:
But I guess the big question now is how can determine for sure if
it's a specifically formatted email that's causing the clamav crashes
and, if so, how can I capture one of the emails?
Hmmm... I know there are some archive milters out there that make a copy of
all
R. Steven Rainwater wanted us to know:
Thanks Todd, this was the first thing I've tried that helped. Prior to
0.87, we were running max children at 25 and never had problems. I
bumped it up to 40 now and that seems to have helped somewhat. We're
still getting a couple of the error messages in the
--- [EMAIL PROTECTED] wrote:
From: R. Steven Rainwater [EMAIL PROTECTED]
Subject: Re: [Clamav-users] clamav-milter seems unstable
with 0.87
To: clamav-users@lists.clamav.net
Thanks Todd, this was the first thing I've tried that
helped. Prior to
0.87, we were running max children at 25 and never
R. Steven Rainwater yazmış:
After upgrading one of our servers to clamav 0.87, we are experience
intermittent failures of clamav-milter which result sendmail refusing
all mail until clamav-milter is restarted. Sometimes it will run for 24
hours or more without crashing but generally it seems to
On Thu, 2005-09-22 at 11:28, Cevher wrote:
R. Steven Rainwater yazmış:
After upgrading one of our servers to clamav 0.87,
we are experience intermittent failures ...
Try with adding --timeout=0 to your CLAMAV_FLAGS variable.
According to the man page 0 is the default value for timeout. But
Update. I tried changing -T=0 to --timeout=0 as one person suggested but
it had no effect. For the moment, I've added a chron job that restarts
clamav-milter hourly, which is at least keeping the mail flowing for
now. If I can't come up with a solution shortly though, I may need to
downgrade back
R. Steven Rainwater wrote:
Update. I tried changing -T=0 to --timeout=0 as one person suggested
but it had no effect. For the moment, I've added a chron job that
restarts clamav-milter hourly, which is at least keeping the mail
flowing for now. If I can't come up with a solution shortly
[EMAIL PROTECTED] wanted us to know:
R. Steven Rainwater wrote:
Update. I tried changing -T=0 to --timeout=0 as one person suggested
but it had no effect. For the moment, I've added a chron job that
restarts clamav-milter hourly, which is at least keeping the mail
flowing for now. If I can't
On Thu, 2005-09-22 at 15:22, [EMAIL PROTECTED] wrote:
R. Steven Rainwater wrote:
Update. I tried changing -T=0 to --timeout=0 as one person suggested
but it had no effect. For the moment, I've added a chron job that
restarts clamav-milter hourly, which is at least keeping the mail
flowing
R. Steven Rainwater wanted us to know:
Have you tried running clamd and using --external on clamav-milter?
Just tried it. Already had two more crashes in less than 10 minutes!
:-( Both were of the write(A) return -1, expected 5: Broken pipe
variety, if that means anything.
Pick up the max
19 matches
Mail list logo
