What happens when you run it from the command line as the Nagios user? I had a similar issue that required the check to run as root.
Luis -----Original Message----- From: Assaf Flatto [mailto:nag...@flatto.net] Sent: Wednesday, May 19, 2010 10:59 AM To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] localhost DOWN messages, return code 127 is out of bounds Michael Maxwell wrote: > Hello, > > Just installed nagios 3.2.1 following the docs at > http://nagios.sourceforge.net/docs/3_0/quickstart.html > > Everything starts up normally, web interface is fine, can login, > enable/disable checks, etc... However, every 2 hours exactly, > I'm getting the following alert in email: > > From: nagios > Subject: ** PROBLEM Host Alert: localhost is DOWN ** > > ***** Nagios ***** > > Notification Type: PROBLEM > Host: localhost > State: DOWN > Address: 127.0.0.1 > Info: (Return code of 127 is out of bounds - plugin may be missing) > > Date/Time: Tue May 18 15:00:15 PDT 2010 > > If I go to check the services, everything is green. > > This is coming from a fresh install with nothing special configured. > > I've googled until my eyes glazed over and no one seems to report > this happening with "localhost". I've checked for the plugins, > checked permissions, etc... The best I can tell, it's all as it > should be. I'm sure I've missed some simple detail somewhere, but > it's eluding me at the moment. > > Any help on solving this problem would be greatly appreciated. > > Below, I've included logfile contents as well as every detail > I could think of on how the system is setup. > > Thanks > > [1274215437] Nagios 3.2.1 starting... (PID=5185)[1274215437] Local > time is Tue May 18 13:43:57 PDT 2010 > [1274215437] LOG VERSION: 2.0 > [1274215437] Finished daemonizing... (New PID=5186)[1274215447] > Warning: Return code of 127 for check of host 'localhost' was out of > bounds. Make sure the plugin you're trying to run actually e > xists. > [1274215447] HOST ALERT: localhost;DOWN;SOFT;1;(Return code of 127 is > out of bounds - plugin may be missing)[1274215477] Warning: Return > code of 127 for check of service 'Current Load' on host 'localhost' > was out of bounds. Make sure the plugin you'r > e trying to run actually exists. > [1274215477] SERVICE ALERT: localhost;Current > Load;CRITICAL;HARD;1;(Return code of 127 is out of bounds - plugin may > be missing)[1274215517] Warning: Return code of 127 for check of host > 'localhost' was out of bounds. Make sure the plugin you're trying to > run actually e > xists. > [1274215517] HOST ALERT: localhost;DOWN;SOFT;2;(Return code of 127 is > out of bounds - plugin may be missing)[1274215517] Warning: Return > code of 127 for check of service 'Current Users' on host 'localhost' > was out of bounds. Make sure the plugin you' > re trying to run actually exists. > [1274215517] SERVICE ALERT: localhost;Current > Users;CRITICAL;HARD;1;(Return code of 127 is out of bounds - plugin > may be missing)[1274215557] Warning: Return code of 127 for check of > service 'HTTP' on host 'localhost' was out of bounds. Make sure the > plugin you're trying > to run actually exists. > [1274215557] SERVICE ALERT: localhost;HTTP;CRITICAL;HARD;1;(Return > code of 127 is out of bounds - plugin may be missing)[1274215587] > Warning: Return code of 127 for check of host 'localhost' was out of > bounds. Make sure the plugin you're trying to run actually e > xists. > [1274215557] SERVICE ALERT: localhost;HTTP;CRITICAL;HARD;1;(Return > code of 127 is out of bounds - plugin may be missing)[1274215587] > Warning: Return code of 127 for check of host 'localhost' was out of > bounds. Make sure the plugin you're trying to run actually e > xists. > [1274215587] HOST ALERT: localhost;DOWN;SOFT;3;(Return code of 127 is > out of bounds - plugin may be missing) > [1274215597] Warning: Return code of 127 for check of service 'PING' > on host 'localhost' was out of bounds. Make sure the plugin you're > trying to run actually exists. > [1274215597] SERVICE ALERT: localhost;PING;CRITICAL;HARD;1;(Return > code of 127 is out of bounds - plugin may be missing) > [1274215627] Warning: Return code of 127 for check of service 'Root > Partition' on host 'localhost' was out of bounds. Make sure the plugin > you're trying to run actually exists. > [1274215627] SERVICE ALERT: localhost;Root > Partition;CRITICAL;HARD;1;(Return code of 127 is out of bounds - > plugin may be missing) > > > Detailed information on the system, what's installed, etc...: > > CentOS 5.4 > Linux [deleted] 2.6.18-194.el5 #1 SMP Fri Apr 2 14:58:35 EDT 2010 i686 > i686 i386 GNU/Linux > > Nagios 3.2.1 > Nagios Plugins 1.4.14 > Apache httpd 2.2.15 > PHP 5.3.2 > > $ grep nagios /etc/passwd > nagios:x:9000:9001::/home/nagios:/bin/bash > > $ grep nag /etc/group > nagcmd:x:9000:apache > nagios:x:9001:nagios > > Options used to build nagios: > ./configure --with-command-group=nagcmd \ > --prefix=/opt/nagios-3.2.1 \ > --with-nagios-user=nagios \ > --with-httpd-conf=/opt/httpd/conf > > Options used to build plugins: > ./configure --with-nagios-user=nagios \ > --with-nagios-group=nagios \ > --prefix=/opt/nagios-3.2.1 > > Permissions of files in /opt/nagios-3.2.1/libexec: > $ ls -l /opt/nagios-3.2.1/libexec/ > total 1360K > -rwxr-xr-x 1 nagios nagios 31052 May 18 13:48 check_apt* > -rwxr-xr-x 1 nagios nagios 2240 May 18 13:48 check_breeze* > -rwxr-xr-x 1 nagios nagios 38078 May 18 13:48 check_by_ssh* > lrwxrwxrwx 1 root root 9 May 18 13:48 check_clamd -> check_tcp* > -rwxr-xr-x 1 nagios nagios 21516 May 18 13:48 check_cluster* > -r-sr-xr-x 1 root nagios 34952 May 18 13:48 check_dhcp* > -rwxr-xr-x 1 nagios nagios 32640 May 18 13:48 check_dig* > -rwxr-xr-x 1 nagios nagios 48280 May 18 13:48 check_disk* > -rwxr-xr-x 1 nagios nagios 8075 May 18 13:48 check_disk_smb* > -rwxr-xr-x 1 nagios nagios 36777 May 18 13:48 check_dns* > -rwxr-xr-x 1 nagios nagios 18705 May 18 13:48 check_dummy* > -rwxr-xr-x 1 nagios nagios 3051 May 18 13:48 check_file_age* > -rwxr-xr-x 1 nagios nagios 6313 May 18 13:48 check_flexlm* > lrwxrwxrwx 1 root root 9 May 18 13:48 check_ftp -> check_tcp* > -rwxr-xr-x 1 nagios nagios 85634 May 18 13:48 check_http* > -r-sr-xr-x 1 root nagios 39620 May 18 13:48 check_icmp* > -rwxr-xr-x 1 nagios nagios 23743 May 18 13:48 check_ide_smart* > -rwxr-xr-x 1 nagios nagios 15132 May 18 13:48 check_ifoperstatus* > -rwxr-xr-x 1 nagios nagios 12518 May 18 13:48 check_ifstatus* > lrwxrwxrwx 1 root root 9 May 18 13:48 check_imap -> check_tcp* > -rwxr-xr-x 1 nagios nagios 7350 May 18 13:48 check_ircd* > lrwxrwxrwx 1 root root 9 May 18 13:48 check_jabber -> check_tcp* > -rwxr-xr-x 1 nagios nagios 30014 May 18 13:48 check_ldap* > lrwxrwxrwx 1 root root 10 May 18 13:48 check_ldaps -> check_ldap* > -rwxr-xr-x 1 nagios nagios 28714 May 18 13:48 check_load* > -rwxr-xr-x 1 nagios nagios 6020 May 18 13:48 check_log* > -rwxr-xr-x 1 nagios nagios 20282 May 18 13:48 check_mailq* > -rwxr-xr-x 1 nagios nagios 25812 May 18 13:48 check_mrtg* > -rwxr-xr-x 1 nagios nagios 24295 May 18 13:48 check_mrtgtraf* > -rwxr-xr-x 1 nagios nagios 28548 May 18 13:48 check_nagios* > lrwxrwxrwx 1 root root 9 May 18 13:48 check_nntp -> check_tcp* > lrwxrwxrwx 1 root root 9 May 18 13:48 check_nntps -> check_tcp* > -rwxr-xr-x 1 nagios nagios 38266 May 18 13:48 check_nt* > -rwxr-xr-x 1 nagios nagios 35917 May 18 13:48 check_ntp* > -rwxr-xr-x 1 nagios nagios 33889 May 18 13:48 check_ntp_peer* > -rwxr-xr-x 1 nagios nagios 31725 May 18 13:48 check_ntp_time* > -rwxr-xr-x 1 nagios nagios 54192 May 18 13:48 check_nwstat* > -rwxr-xr-x 1 nagios nagios 8324 May 18 13:48 check_oracle* > -rwxr-xr-x 1 nagios nagios 30356 May 18 13:48 check_overcr* > -rwxr-xr-x 1 nagios nagios 41387 May 18 13:48 check_ping* > lrwxrwxrwx 1 root root 9 May 18 13:48 check_pop -> check_tcp* > -rwxr-xr-x 1 nagios nagios 39647 May 18 13:48 check_procs* > -rwxr-xr-x 1 nagios nagios 29078 May 18 13:48 check_real* > -rwxr-xr-x 1 nagios nagios 9579 May 18 13:48 check_rpc* > -rwxr-xr-x 1 nagios nagios 1135 May 18 13:48 check_sensors* > lrwxrwxrwx 1 root root 9 May 18 13:48 check_simap -> check_tcp* > -rwxr-xr-x 1 nagios nagios 51895 May 18 13:48 check_smtp* > lrwxrwxrwx 1 root root 9 May 18 13:48 check_spop -> check_tcp* > -rwxr-xr-x 1 nagios nagios 26231 May 18 13:48 check_ssh* > lrwxrwxrwx 1 root root 9 May 18 13:48 check_ssmtp -> check_tcp* > -rwxr-xr-x 1 nagios nagios 30682 May 18 13:48 check_swap* > -rwxr-xr-x 1 nagios nagios 38940 May 18 13:48 check_tcp* > -rwxr-xr-x 1 nagios nagios 28909 May 18 13:48 check_time* > lrwxrwxrwx 1 root root 9 May 18 13:48 check_udp -> check_tcp* > -rwxr-xr-x 1 nagios nagios 34400 May 18 13:48 check_ups* > -rwxr-xr-x 1 nagios nagios 27485 May 18 13:48 check_users* > -rwxr-xr-x 1 nagios nagios 2934 May 18 13:48 check_wave* > -rwxr-xr-x 1 nagios nagios 28787 May 18 13:48 negate* > -rwxr-xr-x 1 nagios nagios 27484 May 18 13:48 urlize* > -rwxr-xr-x 1 nagios nagios 1939 May 18 13:48 utils.pm* > -rwxr-xr-x 1 nagios nagios 862 May 18 13:48 utils.sh* > AFAIK centos has a security mechanism called msec that can some time change the permissions of files and cause this issue . check if you have the msec is working ( usually in the cron.d or cron.hourly or cron.daily directory ) and if so - you may want to set itup so it will not modify any of the nagios plugins or directories permissions. Assaf -- Never,Ever Cut A Deal With a Dragon I am doing a Charity Bike ride On the 27 of June for the Capital to Coast Charity. Please help by Donating http://www.justgiving.com/Lovefilm-capital-to-coast ------------------------------------------------------------------------ ------ _______________________________________________ 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 ------------------------------------------------------------------------------ _______________________________________________ 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
