> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of Nagios > Sent: Thursday, July 19, 2007 7:30 AM > To: Marc Powell > Cc: nagios-users@lists.sourceforge.net > Subject: Re: [Nagios-users] check_http output > > Hello Marc, > > I have downloaded and compiled the source code. > it is working on /usr/lib/nagios/plugin, but not in other directories, > Here is the message that I see on nagios screen: > Critical : (Return code of 126 is out of bounds - plugin may be missing) > > is there any way to set up another directory for custom commands.
Yes, sure. 126 means that the file does not exist in the path that you've specified in the command{} definition. Without any specific detail, I'm going to guess that your command definition for your new plugin uses the $USER1$ macro for the path, which points to /usr/lib/nagios/plugin in resource.cfg. You can either create a new $USERx$ macro there, $USER2$ for example, pointing to your custom path and use that in the command{} definition for your new plugin, or, you can specify the full path in the command_line for the command{} definition instead of using the $USERx$ macros. http://nagios.sourceforge.net/docs/2_0/xodtemplate.html#command -- Marc ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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