From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 13 09:51:03 2005 Return-Path: X-Original-To: freebsd-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 AD32216A41C for ; Wed, 13 Jul 2005 09:51:03 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from postfix4-2.free.fr (postfix4-2.free.fr [213.228.0.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B70E43D4C for ; Wed, 13 Jul 2005 09:51:02 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix4-2.free.fr (Postfix) with ESMTP id 0881E32211C; Wed, 13 Jul 2005 11:51:01 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id E0688405B; Wed, 13 Jul 2005 11:50:59 +0200 (CEST) Date: Wed, 13 Jul 2005 11:50:59 +0200 From: Jeremie Le Hen To: Christophe Yayon Message-ID: <20050713095059.GS39292@obiwan.tataz.chchile.org> References: <61087.192.168.42.2.1121196788.squirrel@webmail.nbux.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <61087.192.168.42.2.1121196788.squirrel@webmail.nbux.com> User-Agent: Mutt/1.5.9i Cc: freebsd-hackers@freebsd.org Subject: Re: nagios and pthreads 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: Wed, 13 Jul 2005 09:51:03 -0000 Hi Christophe, a quick glance at the archives whould have helped you. > i know that we add already discuss about this problem, but is there any > solution for this problem ? > > --- > What's section on nagios website > "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. Some folks from > Yahoo! have reported that using the pthread library causes Nagios to pause > under heavy I/O load, causing some service check results to be lost. > Switching to linuxthreads seems to help this problem, but not fix it. The > lock happens in liblthread's __pthread_acquire() - it can't ever acquire > the spinlock. It happens when the main thread forks to execute an active > check. On the second fork to create the grandchild, the grandchild is > created by fork, but never returns from liblthread's fork wrapper, because > it's stuck in __pthread_acquire(). Maybe some FreeBSD users can help out > with this problem." > --- > > > I have just upgraded to 5.4-STABLE but i encountered again the problem. > Sometimes, there is a nagios forked child process which consume 100% of > CPU. > i have heard that there was perhaps a problem with libc_r reported by > Luigi Rizzo on this list 06/22/2005, but no news since this date... > > My workaround is to have a cron job which run every hour and check if > there is a bad nagios process and kill it... i know it's very ugly... > > Do you any solution or what could i do to get more trace when it happen ? > sorry, but i am not familiar with ktrace like tools... If someone could > help me to help nagios community on freebsd ;-) ? > > Thanks in advance. This thread should countain some answers : http://lists.freebsd.org/pipermail/freebsd-hackers/2005-June/012435.html Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >