NSClient++ Help (#1) - CPULOAD check [SOLVED] (#513) - Message List
When I run the original nsclient I am able to pull CPULOAD info from the nagios server fine.
./check_nt -H IP -p 1248 -v CPULOAD -l 10,80,95,60,80,95,1440,80,95 CPU Load 13% (10 min average) 13% (60 min average) 13% (1440 min average) | '10 min avg Load'=13%;80;95;0;100 '60 min avg Load'=13%;80;95;0;100 '1440 min avg Load'=13%;80;95;0;100
But when I run nscp on the same client I receive the following:
./check_nt -s passphrase -H IP -p 1248 -v CPULOAD -l 10,80,95,60,80,95,1440,80,95 NSClient - ERROR: Could not get data for 10 perhaps we don't collect data this far back?
Client shows this:
d \NSClientListener.cpp(146) Data: passphrase d \NSClientListener.cpp(171) Data: 10 d \NSClient++.cpp(910) Injecting: checkCPU: 10, nsclient e \PDHCollector.cpp(264) Failed to get CPU value: Strange error buffer pointers are f*cked up d \NSClient++.cpp(946) Injected Result: WARNING 'ERROR: Could not get data for 1 0 perhaps we don't collect data this far back?' d \NSClient++.cpp(947) Injected Performance Result:
I know nscp works since I do get results for other nrpe checks
./check_nt -s passphrase -H IP -p 1248 -v SERVICESTATE -l eventlog OK: All services are in their apropriate state.
Client shows this:
d \NSClientListener.cpp(146) Data: passphrase d \NSClientListener.cpp(171) Data: ShowFail?&eventlog d \NSClient++.cpp(910) Injecting: checkServiceState: ShowFail?, eventlog, nsclien t d \NSClient++.cpp(946) Injected Result: OK 'OK: All services are in their apropr iate state.' d \NSClient++.cpp(947) Injected Performance Result:
./check_nt -s passphrase -H IP -p 1248 -v CLIENTVERSION NSClient++ 0.3.5.1 2008-09-24
Client shows this:
d \NSClientListener.cpp(146) Data: passphrase d \NSClientListener.cpp(171) Data:
Any idea what might be going on with the CPULOAD check?
-
Message #1587
Are you trying to use the older nt checks of the NRPE checks?
mike2k02/19/10 14:56:47 (3 years ago) -
Message #1619
The "length of time" you can check is decided by some parameters which is by default 60 minutes (a lot less then 1440 min average).
;# CPU BUFFER SIZE ; Can be anything ranging from 1s (for 1 second) to 10w for 10 weeks. Notice that a larger buffer will waste memory ; so don't use a larger buffer then you need (ie. the longest check you do +1). ;CPUBufferSize=1h ; ;# CHECK RESOLUTION ; The resolution to check values (currently only CPU). ; The value is entered in 1/10:th of a second and the default is 10 (which means ones every second) ;CheckResolution=10
Michael Medin
mickem02/26/10 07:30:19 (3 years ago)
