> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of John Johnson > Sent: Sunday, January 07, 2007 3:55 PM > To: [email protected] > Subject: [Nagios-users] Return code of 137 is out of bounds > > Hi, > > I am running nagios 1.3 and monitoring different services successfully. > I have a problem with the service defined below, I am getting the error > Return code of 137 is out of bounds.
137 or 127? 137 is a very uncommon error. If running on Solaris, this FAQ may be relevant -- http://nagios.org/faqs/viewfaq.php?faq_id=17. If 127, it means that your command_line in your command{} definition is incorrect, specifically that the path to the plugin is incorrect or the plugin file name itself is incorrect. > When I run the check_tcp command from the server I get an ok return. > > Can someone please help me resolve this issue. You'll need to provide OS version, nagios version, how you installed nagios and the plugins (package or source), the command definition for check_tcp, the values for any macros used in that definition and the host definition for ldapsevr1 for us to guess much further. When you performed your test run of the plugin from the command line did you run it as the nagios user exactly as it's defined in your command{} definition? Running a plugin as the nagios user (as nagios does) can result in different behavior than if run as the root user. -- Marc ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
