NSClient++ Help (#1) - NSClient++ unable to get CPU stats until restart (#538) - Message List
Not necessarily a bug or question or anything, I just thought it might be useful to see this data...
A few days ago, one of my Windows Server 2003 R2 hosts in the field began giving me fits regarding its CPU counters:
ERROR: Could not get data for 5m perhaps we dont collect data this far back?
So, I took a look at the nsclient.log file on the server:
2010-03-15 04:45:36: error:modules\CheckSystem\PDHCollector.cpp:264: Failed to get CPU value: \Processor(_total)\% Processor Time: Failed to get mutex :( 2010-03-15 04:50:36: error:modules\CheckSystem\PDHCollector.cpp:264: Failed to get CPU value: \Processor(_total)\% Processor Time: Failed to get mutex :( 2010-03-15 04:55:36: error:modules\CheckSystem\PDHCollector.cpp:264: Failed to get CPU value: \Processor(_total)\% Processor Time: Failed to get mutex :( 2010-03-15 05:00:35: error:modules\CheckSystem\PDHCollector.cpp:264: Failed to get CPU value: \Processor(_total)\% Processor Time: Failed to get mutex :(
This continued until I restarted NSClient++. I am running v0.3.7.494 on this host. Once I restarted the client, everything began working again.
Just mentioning it in case it points to a larger problem. Thanks!
Benny
-
Message #1707
I have seen this popup before and I think (notice think) it might be related to time-outs ie. if a system is very "busy" several requests might get queued and causing deadlocks (which is what the error points at) but I am not sure how to solve it properly. The problem is that threads would need to be closed "nicely" (ie. not killed) so thye are able to free up locks.
unless this becomes a big issue I don't think it is something I will solve at the moment.
Michael Medin
mickem04/14/10 14:05:51 (3 years ago)
