From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 21 14:43:58 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 F335916A41C for ; Tue, 21 Jun 2005 14:43:57 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6DDC43D48 for ; Tue, 21 Jun 2005 14:43:57 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.4/8.13.4/NETPLEX) with ESMTP id j5LEhn8F016140; Tue, 21 Jun 2005 10:43:49 -0400 (EDT) Date: Tue, 21 Jun 2005 10:43:49 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Michal Mertl In-Reply-To: <1119360396.781.17.camel@genius1.i.cz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) 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 Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2005 14:43:58 -0000 On Tue, 21 Jun 2005, Michal Mertl wrote: > Dag-Erling Sm=F8rgrav 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. --=20 DE