Date: Tue, 21 Jun 2005 10:43:49 -0400 (EDT) From: Daniel Eischen <deischen@freebsd.org> To: Michal Mertl <mime@traveller.cz> Cc: Dag-Erling =?ISO-8859-1?Q?Sm=F8rgrav?= <des@des.no>, hackers@freebsd.org, Charles Sprickman <spork@fasttrackmonkey.com> Subject: Re: Nagios and threads Message-ID: <Pine.GSO.4.43.0506211042140.17105-100000@sea.ntplx.net> In-Reply-To: <1119360396.781.17.camel@genius1.i.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 21 Jun 2005, Michal Mertl wrote: > Dag-Erling Sm=F8rgrav wrote: > > Charles Sprickman <spork@fasttrackmonkey.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.43.0506211042140.17105-100000>