THIS KNOWLEDGE BASE HAS BEEN ARCHIVED AND IS NO LONGER BEING UPDATED
Please visit library.nagios.com/docs for the latest and most up-to-date documentation.
Home » Categories » Products » NRPE » Troubleshooting » Common Problems

NRPE - Return Code Of 127 Is Out Of Bounds - Plugin May Be Missing

Problem Description

This KB article addresses the following NRPE error:

Return Code Of 127 Is Out Of Bounds - Plugin May Be Missing

 

Assumed Knowledge

The following KB article contains an explanation of how NRPE works and may need to be referenced to completely understand the problem and solution that is provided here:

NRPE - Agent and Plugin Explained

 

Troubleshooting The Error

This error is usually experienced when the plugin referenced by the command directive in nrpe.cfg is either missing from the libexec folder or the command directive is named incorrectly. It could also imply that the command name passed through NRPE from the Nagios XI server is not defined in the nrpe.cfg file on the remote host.

The first troubleshooting step is to know the name of the command you are requesting NRPE to execute. Referring to the following screenshot from a service definition in the Nagios XI Core Configuration Manager (CCM):

 

 

You can see the command is called:

check_foo

 

On your remote host make sure that the command is defined in nrpe.cfg, for example:

command[check_foo]=/usr/local/nagios/libexec/check_foo.sh $ARG1$


Now that you have identified the command definition, verify the spelling of check_foo in $ARG1$ (in CCM) matches the exact spelling of the command directive name command[check_foo].

Next, make sure the plugin being executed on the remote host actually exists. In this example, the name of the plugin is:

/usr/local/nagios/libexec/check_foo.sh


Execute the following command on the remote host to see if it exists:

ls -la /usr/local/nagios/libexec/check_foo.sh


If it does not exist, then the output would be something like:

ls: cannot access /usr/local/nagios/libexec/check_foo.sh: No such file or directory

 

If this is your problem, you will have to copy the plugin to the /usr/local/nagios/libexec/ folder.

Make sure the filename check_foo.sh has the correct file extension. Different plugins have different file extensions (.sh, .bin, .pl, .py, etc.).  The path must include the extension of the plugin, but the command directive name, wrapped in 'command[]' does not need an extension.

 

 

Final Thoughts

For any support related questions please visit the Nagios Support Forums at:

http://support.nagios.com/forum/



Special Offer For Knowledgebase Visitors! Get a huge discount on Nagios Log Server by clicking below.

Get 60% Off Nagios Log Server!

Did you know? Nagios provides complete monitoring of: Windows, Linux, UNIX, Servers, Websites, SNMP, DHCP, DNS, Email, Storage, Files, Apache, IIS, EC2, and more!

0 (0)
Article Rating (No Votes)
Rate this article
  • Icon PDFExport to PDF
  • Icon MS-WordExport to MS Word
Attachments Attachments
There are no attachments for this article.
Related Articles RSS Feed
NRPE - Remote does not support Version 3 Packets
Viewed 26234 times since Mon, Nov 27, 2017
NRPE - NRPE: Unable To Read Output
Viewed 94797 times since Mon, Jul 17, 2017
NRPE - v3/v4 Compatibility With Previous Versions
Viewed 50392 times since Fri, Jun 24, 2016
NRPE - Connection Refused Or Timed Out
Viewed 10814 times since Mon, Jul 17, 2017
Disabling Port 113 IDENT Requests
Viewed 6974 times since Tue, Mar 12, 2019
How To Clear Solaris Service Maintenance Status
Viewed 34525 times since Mon, Mar 6, 2017
NRPE - Connection Refused By Host
Viewed 16632 times since Mon, Jul 17, 2017
NRPE - Packet Size Explained
Viewed 33286 times since Thu, Jun 30, 2016
NRPE - Warning: This Plugin Must Be Either Run As Root Or Setuid
Viewed 12813 times since Mon, Jul 17, 2017
NRPE - Agent and Plugin Explained
Viewed 75165 times since Fri, Jul 14, 2017