Closed icinga-migration closed 8 years ago
icinga-migration
commented
8 years ago Updated by mfriedrich on 2016-04-07 21:17:19 +00:00
That's most likely the issue from #9157.
icinga-migration
commented
8 years ago Updated by mfriedrich on 2016-04-07 21:17:31 +00:00
icinga-migration
commented
8 years ago Updated by ianconolly on 2016-04-08 14:26:53 +00:00
This is very useful, but does not match my scenario. The hosts in question have perfect connectivity between each other, the system times are in sync, and manually running 'check_nrpe -H remote_host -c check_load' produces a correct response. The out of bounds 255 return code only happens when the check is initiated from the Icinga web interface.
We are currently running Icinga 1.10.3. Would upgrading to a newer version in the v1 platform potentially fix this issue?
icinga-migration
commented
8 years ago Updated by ianconolly on 2016-04-08 16:18:57 +00:00
I have narrowed down the issue to a simple misconfiguration within Icinga. My command line tests all worked because the address and hostnames matched. Our Icinga config had the wrong IP information for remote_host, but we never saw a route issue because the wrong IP in question was still valid.
Thank you, this can be marked as Resolved.
icinga-migration
commented
8 years ago Updated by mfriedrich on 2016-04-14 14:32:55 +00:00
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11546
Created by ianconolly on 2016-04-07 20:09:33 +00:00
Assignee: (none) Status: Rejected (closed on 2016-04-14 14:32:55 +00:00) Target Version: (none) Last Update: 2016-04-14 14:32:55 +00:00 (in Redmine)
Using Icinga 1.10 I have a monitor_host and a remote_host in this scenario using the NRPE plugins to retrieve data. I can run the check_nrpe from the command line of monitor_host to remote_host and get the correwct data I expect. I can run the relevant check (check_load in the case_ on remote_host and also get results. Logs on both servers show the connection, request, and results.
From the Icinga web portal I can perform a force check of the service, but the logs on monitor_host throw the 255 out of bounds and the remote_host never sees the request.
nagios@monitor_host:~$ /usr/lib/nagios/plugins/check_nrpe -H remote_host -c check_load OK - load average: 0.00, 0.01, 0.05|load1=0.000;96.000;144.000;0; load5=0.010;80.000;125.000;0; load15=0.050;60.000;96.000;0;
Command line: Apr 7 15:38:44 remote_host nrpe[6828]: Connection from monitor_host port 36788 Apr 7 15:38:44 remote_host nrpe[6828]: Host address is in allowed_hosts Apr 7 15:38:44 remote_host nrpe[6828]: Handling the connection... Apr 7 15:38:44 remote_host nrpe[6828]: Host is asking for command 'check_load' to be run... Apr 7 15:38:44 remote_host nrpe[6828]: Running command: /usr/lib/nagios/plugins/check_load -w 96,80,60 -c 144,125,96 Apr 7 15:38:45 remote_host nrpe[6828]: Command completed with return code 0 and output: OK - load average: 0.00, 0.01, 0.05|load1=0.000;96.000;144.000;0; load5=0.010;80.000;125.000;0; load15=0.050;60.000;96.000;0; Apr 7 15:38:45 remote_host nrpe[6828]: Return Code: 0, Output: OK - load average: 0.00, 0.01, 0.05|load1=0.000;96.000;144.000;0; load5=0.010;80.000;125.000;0; load15=0.050;60.000;96.000;0; Apr 7 15:38:45 remote_host nrpe[6828]: Connection from monitor_host closed.
nagios@remote_host:~$ /usr/lib/nagios/plugins/check_load -w 96,80,60 -c 144,125,96 OK - load average: 0.00, 0.01, 0.05|load1=0.000;96.000;144.000;0; load5=0.010;80.000;125.000;0; load15=0.050;60.000;96.000;0;
Icinga force check log: [1460057490] EXTERNAL COMMAND: SCHEDULE_FORCED_SVC_CHECK;remote_host;System Load;1460057488 [1460057495] Return code of 255 is out of bounds
*note: hostnames have been made generic
Relations: