On Thu, 2006-01-12 at 16:47 -0600, David Kohn wrote:
Yes it'd be nice if you recompiled with -g flag and gave it another go...
Can do, but if you notice when this thread started, it's been almost 2
months since the last hang, and this time was only on one of the 10 or
so servers I maintain.
Hi,
On 1/11/06, Dale Blount [EMAIL PROTECTED] wrote:
It (finally?) happened again, here's the debugging data I've collected
so far. I've left it running incase you need me to attach gdb to it
(please provide gdb commands you'd like me to run).
Having a look on the debug data you provided
On Thu, 2006-01-12 at 14:22 +0100, Nepenthes Development Team wrote:
Hi,
On 1/11/06, Dale Blount [EMAIL PROTECTED] wrote:
It (finally?) happened again, here's the debugging data I've collected
so far. I've left it running incase you need me to attach gdb to it
(please provide gdb
On 1/12/06, Dale Blount [EMAIL PROTECTED] wrote:
The hung freshclam is still running and I will be happy to run gdb on it
if you provide me the sequence of commands I need to run. Last time I
did something like this I managed to completely crash the hung app
instead of getting more data from
On Thu, Jan 12, 2006 at 03:46:17PM +0100, Nepenthes Development Team said:
http://phpfi.com/95896
thats what i'd recommend to patch this, everything else is _much_ more work.
I'm not sure that SO_RCVTIMEO is fully portable (at last the first docs
I found seem to imply it's not defined
gdb --pid=pid
once attached
bt
will give the backtrace.
Here it is, it's a long one.
# gdb --pid=17435
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute
On 1/12/06, Dale Blount [EMAIL PROTECTED] wrote:
# gdb --pid=17435
GNU gdb 6.3
looks like compiled without debugging symbols to me, so its pretty useless
___
http://lurker.clamav.net/list/clamav-users.html
Yes it'd be nice if you recompiled with -g flag and gave it another go...
Your backtrace does look kind of wacky though. A depth of almost 400
frames??! Also, if you look at the frame addresses, you see a bunch of
bogus-looking addresses like 0x and 0x2020202020, which could imply
On Wed, 2005-11-16 at 21:55 +, Stephen Gran wrote:
On Wed, Nov 16, 2005 at 04:45:51PM -0500, Dale Blount said:
On Wed, 2005-11-16 at 18:39 +, Stephen Gran wrote:
Would it be possible to attach gdb or strace to one of these hung
freshclams before killing them in the future? I have
On closer review, there are 4 more hosts with out of date cvd files but
freshclam is still running (but braindead).
3 of the hosts had the exact same size/date output:
-rw-r--r-- 1 clamav clamav 149286 2005-11-04 08:50 daily.cvd
-rw-r--r-- 1 clamav clamav 2560365 2005-11-04 08:50
Dale Blount said:
Hi List,
Every few months or so when a new clamav comes out, I go to update all
of my servers to the latest version. The last few updates have caused
me a little grief because on restarting of clamd/freshclam, it reports
that freshclam wasn't running. This time I
On Wed, 2005-11-16 at 09:27 -0500, Dale Blount wrote:
Hi List,
Every few months or so when a new clamav comes out, I go to update all
of my servers to the latest version. The last few updates have caused
me a little grief because on restarting of clamd/freshclam, it reports
that freshclam
Dale Blount wrote:
This makes 5 of 8 systems where freshclam stopped being functional. 2
of the 4 above needed kill -9 to die, the other 2 died on a normal
kill signal.
Odd... never had a problem with my two servers. freshclam -d has always
worked, from 0.75.1 to 0.87.1
--
On Wednesday 16 Nov 2005 14:54, Dale Blount wrote:
On Wed, 2005-11-16 at 09:27 -0500, Dale Blount wrote:
Hi List,
Every few months or so when a new clamav comes out, I go to update all
of my servers to the latest version. The last few updates have caused
me a little grief because on
On Wed, 16 Nov 2005 09:27:18 -0500 in
[EMAIL PROTECTED] Dale Blount
[EMAIL PROTECTED] wrote:
Hi List,
Every few months or so when a new clamav comes out, I go to update all
of my servers to the latest version. The last few updates have caused
me a little grief because on restarting of
Please let me know if you need any more information in tracking this
down.
Which distro are you running?
All servers are running ArchLinux Current. I have had this happen on
Slackware in the past.
A long time ago I had problems with
freshclam being unable to resolve any servers to get
This is a bit of a long shot, but try renaming /etc/init.d/freshclam
to /etc/init.d/freshclamd, and remember to update the start/kill symlinks
My startup script is called 'clamav' and it starts both freshclam and
clamd, so I don't think that's it.
Thanks,
Dale
Would it be possible to attach gdb or strace to one of these hung
freshclams before killing them in the future? I have an idea that the
problem may be that attempts to download updates that timeout aren't
getting properly terminated, leaving freshclam in a confused state, but
I am currently
On Wed, 2005-11-16 at 18:12 +, Brian Morrison wrote:
On Wed, 16 Nov 2005 13:05:39 -0500 in
[EMAIL PROTECTED] Dale Blount
[EMAIL PROTECTED] wrote:
Please let me know if you need any more information in tracking
this down.
Which distro are you running?
All servers are
On Wed, 2005-11-16 at 18:39 +, Stephen Gran wrote:
Would it be possible to attach gdb or strace to one of these hung
freshclams before killing them in the future? I have an idea that the
problem may be that attempts to download updates that timeout aren't
getting properly terminated,
On Wed, Nov 16, 2005 at 04:45:51PM -0500, Dale Blount said:
On Wed, 2005-11-16 at 18:39 +, Stephen Gran wrote:
Would it be possible to attach gdb or strace to one of these hung
freshclams before killing them in the future? I have an idea that the
problem may be that attempts to
On Tue, 30 Mar 2004 18:11:05 -0500
Ryan Moore [EMAIL PROTECTED] wrote:
Bill Maidment wrote:
Hi
I'm usinf clamav-0.68-1 and occasionally (once every two weeks) I
get this response
ClamAV update process started at Tue Mar 30 08:46:36 2004
SelfCheck: Database status OK.
ERROR:
Hi,
Bill Maidment wrote:
I'm usinf clamav-0.68-1 and occasionally (once every two weeks) I get
this response
ClamAV update process started at Tue Mar 30 08:46:36 2004
SelfCheck: Database status OK.
ERROR: Maximal time (1200 seconds) reached.
Then the freshclam daemon died.
Anyone else come
23 matches
Mail list logo
