last pid: 75503; load averages: 1.64, 1.39, 1.35 up 35+17:29:03 11:21:07
86 processes: 3 running, 83 sleeping
CPU states: 17.2% user, 0.0% nice, 17.2% system, 0.1% interrupt, 65.4% idle
Mem: 235M Active, 366M Inact, 186M Wired, 46M Cache, 111M Buf, 162M Free
Swap: 4096M Total, 4096M Free
PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
62383 nagios 1 111 0 3536K 2696K CPU2 2 516:02 97.46% nagios
On 4/6/06, Ask List <
[EMAIL PROTECTED]> wrote:
Im not sure which plugin it was.On 4/6/06, Jason Martin <[EMAIL PROTECTED]> wrote:On Thu, Apr 06, 2006 at 03:30:11PM -0700, Ask List wrote:
> We currentlly run nagios 2.0 on FreeBSD 6.0. We noticed the bug that was
> posted at this link: http://nagios.sourceforge.net/docs/2_0/whatsnew.html .
> I have noticed on three occassions where one of the nagios-plugins was hung
It sounds like the problem is plugin based, not Nagios based.
Which plugin was hung / spiked? What exact version of the plugin
was it? So on and so forth..
-Jason Martin
--
If you're not confused, you're not paying attention.
This message is PGP/MIME signed.