Date: Tue, 15 Dec 2009 16:24:16 -0500 From: Linda Messerschmidt <linda.messerschmidt@gmail.com> To: Dan Nelson <dnelson@allantgroup.com> Cc: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: 8.0: OpenSSL stat()'s NLS 500+ times causing extreme system load Message-ID: <237c27100912151324x3003b810v6145e5f5cd163dbf@mail.gmail.com> In-Reply-To: <20091215175320.GR84026@dan.emsphone.com> References: <237c27100912100909i9c0eb95jd348eb594d86c744@mail.gmail.com> <20091214001304.GN84026@dan.emsphone.com> <237c27100912141931w1a9d50c0hf85b9b8e271902eb@mail.gmail.com> <20091215175320.GR84026@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 15, 2009 at 12:53 PM, Dan Nelson <dnelson@allantgroup.com> wrote: > It's defined in src/lib/libc/Makefile, so you should be able to remove that > line, rebuild libc and reinstall, and see whether your performance issue > goes away. I tried that and as you predicted, all the bogus stat calls went away. Unfortunately the performance issue did not. :( Back to the drawing board for me! Upon further inspection, it seems as though for each check, Nagios spawns a process that spawns a process that spawns a process that runs the check. I did "ktrace -i -t w -p (nagiospid)" on Nagios for 30 seconds and the ktrace output contained records from 2365 different processes spawned in that 30 seconds. During that time, I would expect about 800 checks to have run, so it does seem like it's right at 3 processes per check. I just don't think the system can keep up with all that fork()ing without going all out; it's just a limit of the Nagios plugin architecture. But thank you very much for point me in the right direction!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?237c27100912151324x3003b810v6145e5f5cd163dbf>