From owner-freebsd-stable Tue Mar 28 20:37:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from camelot.bitart.com (BITart-45.BITart.com [206.103.221.45]) by hub.freebsd.org (Postfix) with SMTP id 9065C37B55A for ; Tue, 28 Mar 2000 20:37:41 -0800 (PST) (envelope-from gerti@bitart.com) Received: (qmail 3095 invoked by uid 101); 29 Mar 2000 04:37:47 -0000 Message-ID: <20000329043747.3094.qmail@camelot.bitart.com> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) In-Reply-To: <20000328204948.K21029@fw.wintelcom.net> X-Nextstep-Mailer: Mail 4.2mach (Enhance 2.2p1) Received: by NeXT.Mailer (1.148) From: Gerd Knops Date: Tue, 28 Mar 2000 22:37:46 -0600 To: Alfred Perlstein Subject: Re: Random signal 9 (SIGKILL), please help! Cc: gerti-freebsds@bitart.com, freebsd-stable@FreeBSD.ORG Reply-To: gerti-freebsds@BITart.com References: <20000329041104.3028.qmail@camelot.bitart.com> <20000328204948.K21029@fw.wintelcom.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > * Gerd Knops [000328 20:36] wrote: > > Hello, > > > > I have a large software package running on a lot of machines and > > several Unixes. > > > > Only on the FreeBSD systems I see that child processes occasionaly > > get killed bya signal 9, and I just can't figure out why. > > > > Syslog does not give any indication. The machines do not swap (I > > know processes mayget killed when the systems run out of swap > > space). The times at which the processesare killed does seem to > > be random, meaning it does not seem dome house keeping codethat > > causes it. > > > > The processes are spawned from various daemons, and are killed > > at different pointsin their existence, even when just barely > > started and no resources to mention areconsumed yet. > > > > All processes run as root, so 'limit' should not be the cause. > > > > Is there anything else but the swapper that can trigger a 'signal > > 9' to be sent toprocesses? > > > > The systems in question run a variety of versions, starting from > > 3.2 Release to afairly recent (4 weeks) 3.4 stable. > > > > Any tips and ideas would be more than welcome. > > Please wrap lines at 70 characters. > > This is on all the FreeBSD systems? This is really confusing I've > _never_ heard of this happening, do you have any machines built > with the same _exact_ hardware exibiting the same problems or not? > Nope, different hardware, all Intel CPUs, some Pentium Pro, some Pentium II, ASUS and Gigabyte motherboards. > Have you tried 4.0? Without some sample code this is going to > be very hard to reproduce. > The code is >50k lines of perl... No I have not tried 4.0 yet. And I can not reproduce the problem either, it just randomly appears at a very low rate. 23 machines running FreeBSD, and I see about 1 to 3 of those a day. > Are you sure you aren't running out of process slots? What is > maxusers set to in the kernel? 64. > How many processes typically run at the same time? > Varying, the busiest machine peaks at about 100 processes, but I have seen it on machines running only 50 processes. Thanks for responding! Gerd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message