On Thu, Mar 03, 2005 at 04:53:58PM -0500, Matt Kettler wrote: >At 04:40 PM 3/3/2005, George Georgalis wrote: >>This log entry indicates when I booted into 2.6.11: >>2005-03-02 12:05:47.018334500 2005-03-02 17:05:47 [781] i: server killed >>by SIGTERM, shutting down > >Is there any chance you're running out of memory and the OOM killer is >kicking in and sending SIGTERM's to spamd's? >
No. There is 1Gb of memory on a very lightly loaded box, and no memory intensive SA rules. That SIGTERM was immedatly prior to the first time I booted 2.6.11, where SA does not work (once) for remote connections (scores 0/0). The problem is resolved running 2.6.8.1, where SA has been flawless for a while. Just occured to me the big gaint lock (new between the versions) has been enabled, could it be related? Below is a post to LKML from today. I recall a problem a while back with a pipe from /proc/kmsg that was sent by root to a program with a user uid. The fix was to run the logging program as root. Has that protected pipe method been extended since 2.6.8.1? ... SA has stopped stdout logging completely with 2.6.11 in addition to the all pass score. But the message seems to go through my temp queue (for testing) and sent on to my local MDA. I'm not sure if it's a sa problem with the kernel or the new kernel doing something new with pipes from tcp connections. Maybe the new kernel is not making files available (eg 0 bytes), until the writing pipe is closed? That would make my SA test a zero byte file, which would pass, close, become full, and the file piped to local MDA is full? ...humm then I'd get a score of "0/5"... this sounds like a SA problem with the new kernel, ideas? // George -- George Georgalis, systems architect, administrator Linux BSD IXOYE http://galis.org/george/ cell:646-331-2027 mailto:[EMAIL PROTECTED]
