On Mar 24, 2005, at 1:12 PM, Elizabeth Schwartz wrote:
This sounds like exactly what I was experiencing. Did the latest build
fix it for you? Turning off clamd and running clamav-milter without
the --external flag seems to have fixed it for me.
Hi Betsy-
See my followup message on March 17th, but
On Mon, 7 Mar 2005 19:52:55 -0500, David Blank-Edelman <[EMAIL PROTECTED]>
wrote:
> I just wanted to pop in and provide the latest update on our saga
> (clamd 0.83 just stops playing nice after running for a while) with
> some more interesting information like stack traces.
This sounds like exact
Howdy-
Now that > a week has gone by with absolutely no problems with our
clamd hanging, I thought I would write in to provide the good news that
I think we have this problem licked. Though we also rev'd exim on Wed,
I think it was the upgrade for 0.83 to devel-20050308 that solved our
probl
On Tue, 08 Mar 2005 08:48:41 +0100
Thomas Lamy <[EMAIL PROTECTED]> wrote:
> This definitely looks like a mail scan with 17 attachments (or level
> of attachments?), and a threadmanager after a database update,
> waiting for the mail scan to finish.
> Tomasz? Trog?
Does the current CVS version f
On Tue, 2005-03-08 at 08:48 +0100, Thomas Lamy wrote:
> David Blank-Edelman schrieb:
> >
> > Today I managed to catch clamd in a hung state and so I poked and
> > prodded at it with gdb. Btw, by hung I mean that attempts to contact
> > clamd on the local socket failed with "connection refused"
David Blank-Edelman schrieb:
Howdy-
I just wanted to pop in and provide the latest update on our saga (clamd
0.83 just stops playing nice after running for a while) with some more
interesting information like stack traces.
Last we left off I had just upped the ulimit for the clamd process from
Howdy-
I just wanted to pop in and provide the latest update on our saga
(clamd 0.83 just stops playing nice after running for a while) with
some more interesting information like stack traces.
Last we left off I had just upped the ulimit for the clamd process from
the default of 256 fds to 102
Igor Brezac said:
>
> On Sat, 19 Feb 2005, James Lick wrote:
>>
>
> I am at Generic_117171-15, which is a lot newer and I am affraid the
> latest patch is giving me problems. ;(
>
> --
> Igor
I'm using the same version with no problem. It works fine. Here are my
clamav build directives - it has w
On Sat, 19 Feb 2005, James Lick wrote:
Igor Brezac wrote:
This is how .80 ran for me. The recent service pack may have done this.
What is your os version, uname -v?
SunOS tcp.com 5.9 Generic_112233-11 sun4u sparc SUNW,Ultra-2 Solaris
I am at Generic_117171-15, which is a lot newer and I am affra
Igor Brezac wrote:
This is how .80 ran for me. The recent service pack may have done
this. What is your os version, uname -v?
SunOS tcp.com 5.9 Generic_112233-11 sun4u sparc SUNW,Ultra-2 Solaris
--
James Lick -- éåæ -- [EMAIL PROTECTED] -- http://jameslick.com/
__
James Lick said:
> Igor Brezac wrote:
>
>> On Fri, 18 Feb 2005, James Lick wrote:
>>
>>>
>>> My clamd is at 12mb process size currently. I haven't noticed memory
>>> bloat in recent versions.
>>>
>>
>> This is the starting clamd memory footprint. How many messages are
>> you scanning? 0.80 ran f
On Sat, 19 Feb 2005, James Lick wrote:
Igor Brezac wrote:
On Fri, 18 Feb 2005, James Lick wrote:
My clamd is at 12mb process size currently. I haven't noticed memory
bloat in recent versions.
This is the starting clamd memory footprint. How many messages are you
scanning? 0.80 ran fine, I not
Igor Brezac wrote:
On Fri, 18 Feb 2005, James Lick wrote:
My clamd is at 12mb process size currently. I haven't noticed memory
bloat in recent versions.
This is the starting clamd memory footprint. How many messages are
you scanning? 0.80 ran fine, I noticed the problem since 0.81...
It proc
On Fri, 18 Feb 2005, David Blank-Edelman wrote:
;
; Thanks for taking the time to look into this with me.
You could try the attached patch, which makes clamd increase its file
descriptor limit to the OS's maximum or the maximum safe value if
you're using select().
A.diff -r -u clamav-devel/clamd
Hmmm.
David Blank-Edelman wrote:
On Feb 18, 2005, at 2:49 PM, Andy Fiddaman wrote:
The accept debug will at least tell us if you're running out of file
descriptors..
Roger.
...
# pfiles `pgrep clamd` | grep rlimit
Current rlimit: 256 file descriptors
Current rlimit: 256 file descriptors
und
On Feb 18, 2005, at 2:49 PM, Andy Fiddaman wrote:
The accept debug will at least tell us if you're running out of file
descriptors..
Roger.
# ndd /dev/tcp tcp_time_wait_interval
6
# pfiles `pgrep clamd` | grep rlimit
Current rlimit: 256 file descriptors
Current rlimit: 256 file descriptors
On Fri, 18 Feb 2005, David Blank-Edelman wrote:
; On Feb 18, 2005, at 4:12 AM, Trog wrote:
;
; > This really looks like you're running out of some resource. That accept
; > () failure is from the clamd primary socket. We will need to find out
; > what the error is. Please try this patch:
;
; Hi Tr
On Feb 18, 2005, at 4:12 AM, Trog wrote:
This really looks like you're running out of some resource. That accept
() failure is from the clamd primary socket. We will need to find out
what the error is. Please try this patch:
Hi Trog and Andy-
Thanks for your responses. I've just patched my sources
On Fri, 18 Feb 2005, James Lick wrote:
Igor Brezac wrote:
On Thu, 17 Feb 2005, David Blank-Edelman wrote:
Solaris 9, gcc built, Solaris 9 stock zlib (1.1.4)
I'm running clamd 0.83 on Solaris 9 compiled with gcc 3.4.2 and zlib 1.2.2.
The older zlib releases have been known to cause clamd to crash,
On Fri, 18 Feb 2005, David Blank-Edelman wrote:
From: Igor Brezac <[EMAIL PROTECTED]>:
How much memory does your clamd process consume when it stops running?
Hi Igor-
I haven't checked (the machine it is running on has plenty of memory and
swap), but I will check next time this happens. Would y
On Fri, 18 Feb 2005 09:12:45 +, Trog <[EMAIL PROTECTED]> wrote:
> This really looks like you're running out of some resource. That accept
> () failure is from the clamd primary socket. We will need to find out
> what the error is. Please try this patch:
> ...
We had a similar problem - Solar
On Thu, 17 Feb 2005, David Blank-Edelman wrote:
; Hi-
; Thanks for such a great program and all of the work being put into it. We're
; having a nasty problem with clamd 0.8x (even with 0.83 which we just installed
; yesterday). After running for a while, it will decide to just stop functioning
;
On Thu, 2005-02-17 at 23:52 -0500, David Blank-Edelman wrote:
> Hi-
>Thanks for such a great program and all of the work being put into
> it. We're having a nasty problem with clamd 0.8x (even with 0.83 which
> we just installed yesterday). After running for a while, it will decide
> to just
(sorry for the weird quoting format and the breaking of the threading,
I just switched myself back off digest mode so I don't have an easy way
to respond to single messages for another message or two)
From: James Lick <[EMAIL PROTECTED]>:
I'm running clamd 0.83 on Solaris 9 compiled with gcc 3.4
On Fri, Feb 18, 2005 at 12:01:12AM -0500, Igor Brezac wrote:
> On Thu, 17 Feb 2005, David Blank-Edelman wrote:
>
> >Hi-
> > Thanks for such a great program and all of the work being put into it.
> >We're having a nasty problem with clamd 0.8x (even with 0.83 which we just
> >installed yesterday)
From: Igor Brezac <[EMAIL PROTECTED]>:
How much memory does your clamd process consume when it stops
running?
Hi Igor-
I haven't checked (the machine it is running on has plenty of memory
and swap), but I will check next time this happens. Would you be
willing to share your build configurati
Igor Brezac wrote:
On Thu, 17 Feb 2005, David Blank-Edelman wrote:
Solaris 9, gcc built, Solaris 9 stock zlib (1.1.4)
I'm running clamd 0.83 on Solaris 9 compiled with gcc 3.4.2 and zlib
1.2.2. The older zlib releases have been known to cause clamd to crash,
so you might want to try that first.
On Thu, 17 Feb 2005, David Blank-Edelman wrote:
Hi-
Thanks for such a great program and all of the work being put into it.
We're having a nasty problem with clamd 0.8x (even with 0.83 which we just
installed yesterday). After running for a while, it will decide to just stop
functioning and retu
Hi-
Thanks for such a great program and all of the work being put into
it. We're having a nasty problem with clamd 0.8x (even with 0.83 which
we just installed yesterday). After running for a while, it will decide
to just stop functioning and return failures or refuse connect from the
MTA. He
29 matches
Mail list logo
