From owner-freebsd-questions@FreeBSD.ORG Mon Feb 4 23:58:08 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C92316A41B for ; Mon, 4 Feb 2008 23:58:08 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 0F42613C442 for ; Mon, 4 Feb 2008 23:58:07 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m14NRnQR049482; Mon, 4 Feb 2008 18:27:49 -0500 (EST) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id m14NRmmt017027 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Feb 2008 18:27:49 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200802042327.m14NRmmt017027@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 04 Feb 2008 18:30:00 -0500 To: Jarrod Sayers From: Mike Tancsa In-Reply-To: References: <59DD6CCE263ECD75A7283A7B@ganymede.hub.org> <477A72B8.8010307@protected-networks.net> <477BAD2B.8070603@tomjudge.com> <1DB78354-EBA2-43D0-A2D6-EFDA4950135B@netleader.com.au> <477C1629.1030604@tomjudge.com> <20080103104129.T36551@wallace.netleader.com.au> <738861275EBE2BF6D27F547B@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: Tom Judge , freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Nagios + 6.3-RELEASE == Hung Process X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2008 23:58:08 -0000 At 06:17 PM 2/4/2008, Jarrod Sayers wrote: >On 03/01/2008, at 11:56 AM, Marc G. Fournier wrote: >>As noted in my original report, this isn't a nagios issue per se ... >>my first >>experience with this issue was with Azureus/java ... so its a >>'threading issue >>in general' ... > >A patch to force the package to link against libthr() has been >committed [1] and should be available once mirrors update as >net-mgmt/ nagios 2.10_1. This has been tested since this >conversation stated in >the net-mgmt/nagios-devel port [2] without any negative feedback being We have been using nagios linked against libthr via libmap.conf since the end of November and its been working great since then. Prior to that, we would see 100% CPU usage a couple of times a week on various nagios procs. Hasnt happened since. ---Mike