Nagios Support Forum

I've got more information on this problem we have been having.

It is indeed on windows machines and most likely from an update. But I did learn that we are using nrpe and do have an agent on one computer at each site.

So, using nagios-nrpe, only the CPU service is givine me a problem What/if any information can I provide to try and resolve this?

Thanks!

Specific status details output on what is being returned to Nagios, and also logging from that application on the windows machine, just a heads up that that agent is depreciated at this point and NCPA/NSClient is now used as a standard for active windows monitoring.

Thanks for that information. I have been trying to tell my manager to move-on to Nagios XI, but he is hard to convince.

Here are some logs as well as the output from the return when I browse the agent and run the check manually, any help is really appreciated. the host with the agent is 192.168.20.23 and it happens to be the same server that has the issue returning the check for CPU. I bolded it below:

2014-03-06 00:14:47 192.168.20.23 GET /nagios/service1.asmx/cpu server=192.168.20.23&param=80 80 - 192.168.234.16 nagios-check_wsc+1.3 - 200 0 0 62
2014-03-06 00:15:05 192.168.20.23 GET /nagios/service1.asmx/uptime server=192.168.20.21&param=4 80 - 192.168.234.16 nagios-check_wsc+1.3 - 200 0 0 77
2014-03-06 00:15:43 192.168.20.23 GET /nagios/service1.asmx/disks server=192.168.20.23&param=20%,10%,exclude:F: 80 - 192.168.234.16 nagios-check_wsc+1.3 - 200 0 0 62
2014-03-06 00:15:43 192.168.20.23 GET /nagios/service1.asmx/uptime server=192.168.20.23&param=4 80 - 192.168.234.16 nagios-check_wsc+1.3 - 200 0 0 62
2014-03-06 00:16:49 192.168.20.23 GET /nagios/service1.asmx/disks server=192.168.20.21&param=20%,10%,exclude:F: 80 - 192.168.234.16 nagios-check_wsc+1.3 - 200 0 0 93
2014-03-06 00:16:49 192.168.20.23 GET /nagios/service1.asmx/disks server=192.168.20.22&param=20%,10%,exclude:F: 80 - 192.168.234.16 nagios-check_wsc+1.3 - 200 0 0 109
2014-03-06 00:16:49 192.168.20.23 GET /nagios/service1.asmx/uptime server=192.168.20.22&param=4 80 - 192.168.234.16 nagios-check_wsc+1.3 - 200 0 0 140
2014-03-06 00:17:15 192.168.20.23 GET /nagios/service1.asmx/cpu server=192.168.20.22&param=80 80 - 192.168.234.16 nagios-check_wsc+1.3 - 200 0 0 1201
2014-03-06 00:18:05 192.168.20.23 GET /nagios/service1.asmx/uptime server=192.168.20.21&param=4 80 - 192.168.234.16 nagios-check_wsc+1.3 - 200 0 0 93
2014-03-06 00:18:43 192.168.20.23 GET /nagios/service1.asmx/disks server=192.168.20.23&param=20%,10%,exclude:F: 80 - 192.168.234.16 nagios-check_wsc+1.3 - 200 0 0 78
2014-03-06 00:18:43 192.168.20.23 GET /nagios/service1.asmx/uptime server=192.168.20.23&param=4 80 - 192.168.234.16 nagios-check_wsc+1.3 - 200 0 0 93
2014-03-06 00:19:50 192.168.20.23 GET /nagios/service1.asmx/disks server=192.168.20.21&param=20%,10%,exclude:F: 80 - 192.168.234.16 nagios-check_wsc+1.3 - 200 0 0 109
2014-03-06 00:19:50 192.168.20.23 GET /nagios/service1.asmx/disks server=192.168.20.22&param=20%,10%,exclude:F: 80 - 192.168.234.16 nagios-check_wsc+1.3 - 200 0 0 109
2014-03-06 00:19:50 192.168.20.23 GET /nagios/service1.asmx/uptime server=192.168.20.22&param=4 80 - 192.168.234.16 nagios-check_wsc+1.3 - 200 0 0 124
2014-03-06 00:21:05 192.168.20.23 GET /nagios/service1.asmx/uptime server=192.168.20.21&param=4 80 - 192.168.234.16 nagios-check_wsc+1.3 - 200 0 0 78
2014-03-06 00:21:16 192.168.20.23 GET /nagios/service1.asmx/cpu server=192.168.20.21&param=80 80 - 192.168.234.16 nagios-check_wsc+1.3 - 200 0 0 1076


Here is when I check it from the agent's gui through a browser
<?xml version="1.0" encoding="UTF-8"?>
<string xmlns="http://nagios-wsc/">Result: CPU UNKNOWN; Load=<null>|<br> cpu=0%;20;60;;</string>

Hmm, looks like the check is not detecting the CPU, are there any special permissions you used while installing this agent? Was it not installed with administrator access? Is this same check working on another system?