Re: [Clamav-users] clamd: Segmentation Fault?

Loren Salsgiver Thu, 26 Feb 2004 22:13:25 -0800

Same issue, I had .65 binary running, tried re-compiling both .65 and .67 when it released. clamd just dies and milter connections go thru the roof...

Feb 26 04:23:52 em1 clamav-milter[4570]: hit max-children limit (300 >= 300): waiting for some to exit Feb 26 04:23:54 em1 clamav-milter[4570]: hit max-children limit (303 >= 300): waiting for some to exit Feb 26 04:23:58 em1 clamav-milter[4570]: hit max-children limit (307 >= 300): waiting for some to exit Feb 26 04:23:59 em1 clamav-milter[4570]: hit max-children limit (310 >= 300): waiting for some to exit root 24481 0.0 0.0 1500 452 ? S 04:24 0:00 grep clamd

The folowing script run every two minutes has been my only work around... I'm sure there are better programmers on the list so please ignore my crude programming...

#! /bin/sh
#
if [ -s /var/log/clamav/alert ]
then
        rm /var/log/clamav/alert
fi

tail -100 /var/log/maillog > /var/log/clamav/test_clam
grep max-child /var/log/clamav/test_clam > /var/log/clamav/alert.pass1
grep clam /var/log/clamav/alert.pass1 > /var/log/clamav/alert
grep /var/run/clamav /var/log/clamav/test_clam >> /var/log/clamav/alert

if [ -s /var/log/clamav/alert ]
then
        ps aux | grep clamd >> /var/log/clamav/alert
        /etc/rc.d/init.d/clamd stop
        rm /var/lock/subsys/clamd
        /etc/rc.d/init.d/clamd start
        /etc/rc.d/init.d/clamav-milter restart
        mail [EMAIL PROTECTED] < /var/log/clamav/alert
fi

In fact .67 seems even less stable than .65. The following from clamd.log...

Thu Feb 26 04:13:59 2004 -> ERROR: ScanStream: accept() failed.
Thu Feb 26 04:14:21 2004 -> ERROR: ScanStream: accept() failed.
Thu Feb 26 04:14:22 2004 -> ERROR: ScanStream: accept() failed.
Thu Feb 26 04:18:00 2004 -> Segmentation fault :-( Bye..

I'm afraid we just may have to abandon clamav if we can't get this stable. For reference the box is a penguin computing dual xeon 2.4ghz with hyper threading, 2 2gb ram, scsi disk, running redhat 9, kernel-2.4.20-28.9, kernel-smp-2.4.20-28.9, and clam .67 compiled on the box with milter, spamd called out of procmail, handling 218,186 messages yesterday finding 490 viruses.

Loren

Thomas Lamy wrote:

Philipp Grosswiler wrote:

Unfortunately, clamd crashed today morning at 05:00 (almost exactly at
05:00). I only realized it by accident. This is what the log is showing:

Thu Feb 26 04:58:10 2004 -> stream: Worm.MyDoom.E.UPX FOUND
Thu Feb 26 05:01:21 2004 -> Segmentation fault :-( Bye..
Thu Feb 26 05:11:18 2004 -> SelfCheck: Database status OK.
Thu Feb 26 05:43:48 2004 -> ERROR: accept() failed
Thu Feb 26 05:43:52 2004 -> ERROR: accept() failed
Thu Feb 26 05:43:56 2004 -> ERROR: accept() failed
Thu Feb 26 05:43:57 2004 -> ERROR: accept() failed

What could cause something like this? How can I prevent it from happening
again?

I am running freshclam every hour (and it was also running at 05:00
exactly).

Any help appreciated.

Which version exactly? On which OS/Distribution? Did you compile from source or installed a binary (from where did you get it)?

Thomas


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users

Re: [Clamav-users] clamd: Segmentation Fault?

Reply via email to