On Mon, 31 Jan 2005, N Fung wrote: > > --- Stefan Hornburg <[EMAIL PROTECTED]> wrote: > > > On Mon, 31 Jan 2005 10:38:13 +0100 (MET) > > Mipam <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > > > I noticed running clam 0.80 (yes i should update > > quickly) that > > > clamd exited: > > > > > > Jan 29 20:14:00 relay3 kernel: pid 553 (clamd), uid > > 106: exited on signal > > > 11 > > > > > > Any hints what this could be? Not hardware failure i > > hope? > > > > 11 is segmentation fault, which can be a software bug, > > hardware problem > > or lack of system resources (memory). > > I'm seeing quite a few signal-11 with my clamav-milter too: > > pid 47506 (clamav-milter), uid 32768: exited on signal 11 > > Other than knowing that it *sometimes* signal-11 when > clamav-milter intercepted an infected message, it doesn't > happen all the time. Anyone knows how to track down the > exact cause? > > I've got 0.81 running on 3 different FreeBSD 4.x systems. > None of the machines are heavily loaded but the signal-11 > happens on two of the machines.
I am running clam on 5.2.1 and 5.3-Stable from FreeBSD. I must add that i am running /var/amavis on a swap backed memory filesystem, so that operations on /var/amavis are not limited to disk i/o. This speeds the process of scanning mails up significantly. Today i upgraded all the clams to 0.81 and it seems to be holding now. Only on one machine i entountered the signal 11. the machine has 2 gigs of ram, 490 meg was actively used, 480 meg was reserved for /var/amavis (running 18 amavis processes to be able to handle lots of mails). Bye, Mipam. _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
