monitor cpu usage...

[Craig A]

>
> could you perhaps paste relevant pieces of check_proc using -vvv?
> just out of interest, how did you install nagios-plugins on this host?
> package or compiled?
>
>
>
Hmm, that's interesting - i didn't know about '-vvv' - lots of useful info
there.   Nagios-plugins on this host was compiled.   By this time, our
offending process (a jvm) is now behaving normally and has stopped consuming
100% constantly.    But when we stress the server manually, if I watch
'top', i can see % CPU for that process go above 60% for several seconds
(ie. if i hit 'space bar' for 2-3 seconds, it's pinned at 60% for a few
seconds, then it goes back to normal {ie. < 1%}).     But if i constantly
run 'check_procs' (as a dummy test, i threw it in a loop and had it run 100
times with no sleep and log the results), it still doesn't view the java
process as above 0%...

If i try exactly the same thing (running check_procs 100 times) with a
non-jvm process (ie. i used '-C top' and then hit space bar to push top
above 20% usage), check_procs reports properly.

Any idea why I'd be getting this descrepancy?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20081216/26595705/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null