(Return code of 25 is out of bounds)

[bosecorp]

I am getting this error in multiple devices and for different type of checks

[cmerchant]

Can you tell us what plugins you are using?

[bosecorp]

the basic plug ins.

[jolson]

Please select one of your problem services and navigate to Configure -> Re-configure this service as indicated in my screenshot.

Once you select 'Re-configure this service' you will see a page appear with a category called "Monitor the service with this command ... (Advanced users only)"

Please post the string that is inside of that category. An example string is:

Code: Select all

check_local_procs!2:10!2:20!httpd!!!!!

[lmiltchev]

This seems like NSClient++ check (correct me if I am wrong). Can you show us one of the failing checks, run from the command line, along with the output of it?

If these are indeed NSClient++ checks, run the following commands and show us the output (hide sensitive info):

Code: Select all

nmap <client ip> -p 12489,5666
/usr/local/nagios/libexec/check_nt -H <client ip> -s <password> -p 12489 -v CLIENTVERSION

[bosecorp]

HI lmiltchev

we are not using NSClient++.

this is happening even in network devices

[bosecorp]

Hi Jolson

here is the output

check_xi_service_wmiplus!'[email protected]'!'mypassword'!checkcpu!-w '80' -c '90'

[jdalrymple]

this is happening even in network devices

Wow - so even snmp checks or similar type active agentless checks are giving this error? Is it possible this is related to some of the gearman changes we've been making? Is it possible that you relocated some service checks off to servers that don't have the appropriate plugins?

I did a quick google of ways in which mod_gearman could cause 25 return codes and nothing jumps out at me, but that doesn't mean we can't be running across a new feature

We'll probably want to run one of the commands from the command line like we did before, and preferably from the server which the check is coming from.

[bosecorp]

HI jdalrymple

Yes, even SNMP.

I did a quick test from the GUI with one of the clients. I force a immediate check and only 1 service came back OK out the 6 that this particular client has.

I did it again but now I did it per services and service came back OK.

I think you are right, this could be related to the changes that we have been making.

I verify the last check on some the services with this error and it has been several minutes since the last check. I think something is causing this problem and the system is taking too long to do the checks.

if you think this is related to the other issue, then we could close this ticket

[jdalrymple]

The GUI test cannot be relied upon. Really the tests need to be run from the command line to get accurate results. In the case of your posted service it would be something like:

Code: Select all

[root@nagiosxi ~]# /usr/local/nagios/libexec/check_wmi_plus.pl -H mywindowshost -u [email protected] -p mypassword -m checkcpu -w '80' -c '90'