From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 1 20:25:53 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4D6D16A41C; Fri, 1 Jul 2005 20:25:53 +0000 (GMT) (envelope-from mime@traveller.cz) Received: from ss.eunet.cz (ss.eunet.cz [193.85.228.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5801443D1F; Fri, 1 Jul 2005 20:25:52 +0000 (GMT) (envelope-from mime@traveller.cz) Received: from localhost.i.cz (ss.eunet.cz [193.85.228.13]) by ss.eunet.cz (8.13.1/8.13.1) with ESMTP id j61KPlTB038338; Fri, 1 Jul 2005 22:25:48 +0200 (CEST) (envelope-from mime@traveller.cz) From: Michal Mertl To: Daniel Eischen In-Reply-To: <1119455157.1401.9.camel@genius1.i.cz> References: <1119455157.1401.9.camel@genius1.i.cz> Content-Type: text/plain Date: Fri, 01 Jul 2005 22:25:46 +0200 Message-Id: <1120249546.749.25.camel@genius1.i.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Dag-Erling =?ISO-8859-1?Q?Sm=F8rgrav?= , hackers@freebsd.org, Charles Sprickman Subject: Re: Nagios and threads X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2005 20:25:53 -0000 On Wed, 22 Jun 2005, I wrote: > Daniel Eischen wrote: > > On Tue, 21 Jun 2005, Michal Mertl wrote: > > > > > Dag-Erling Smrgrav wrote: > > > > Charles Sprickman writes: > > > > > 1. FreeBSD and threads. On FreeBSD there's a native user-level > > > > > implementation of threads called 'pthread' and there's also an > > > > > optional ports collection 'linuxthreads' that uses kernel hooks. > > > > > > > > This is only the case for FreeBSD 4. FreeBSD 5 has native threads. > > > > > > Yes, the description on Nagios page is not precise but unfortunately > > > Nagios still has some problems even on 5.4. I wasn't able to find out > > > what was wrong and the problem dissappeared when I had to replace the > > > computer with single-processor one. The symptoms I observed were that > > > every several days one Nagios process was consuming all the CPU doing > > > hundreds of thousands of syscalls per second. It got always stuck around > > > the time when the the daily cron job run. > > > > > > I did a ktrace on the stuck process and tried to abort it to have the > > > core but I've lost the ktrace output and it never saved the core :-(. > > > > > > I'll install it on another machine and try to diagnose the problem some > > > more. > > > > You gotta try it on -stable. > > OK. I installed Nagios on a SMP computer with fresh -stable. I tried to > stress the disk but until now Nagios hasn't hung. > > Michal Just FYI - I really wasn't able to provoke the hang. I've no idea if the reason is my upgrade to STABLE or something else. I can only confirm what went on this thread - Nagios seems to have lots of short lived children (for the tests) which are probably created with fork and the main process is multithreaded. Michal