Hi! Kaplan, Andrew H. pravi: >> If i understand correctly, u ran the plugin su'ed to the nagios user and >> the command completed successfully? > > That is correct. > >> If that's the case, then please check if the xinetd daemon is running >> and what the setting for nagios-nrpe are for xinetd. > > As far as the client is concerned, nrpe is not being run via xinetd, it is > being > run as a standalone daemon. This is command syntax that is used for > running the daemon: > > /usr/local/nagios/bin/nrpe -c /usr/local/nagios/etc/nrpe.cfg -d
Have you checked the setting in the nrep.cfg file? Like server_port, allowed_hosts, nrpe_user, nrpe_group? I actaully have only one box, that's running NRPE as a standalone daemon. U have to add the server IP in the allowed_hosts section (add the server to /etc/hosts.allow as well). And u need to restart the daemon on every change. If u got all the above set up correcty, then i'm affraid i'm out of ideas... :o( Regards, D. > > The user account running the daemon is nagios. This account has its own > home directory, password, and uses the /bin/bash shell. > > As far as the server is concerned, nrpe is not present in xinetd, but does > have > a startup script in the /etc/init.d directory. It is currently not turned on, > but it can be if so needed. > >> What's your NRPE version on the server and the client machine? > > The version of NRPE on the server is 2.5.1, and this is the package that came > bundled with the operating system which is Fedora Core 5. > The version of NRPE on the client is also 2.5.1. The difference between that > on > the server and client is that the client was compiled from source. Also, even > though the client version is 2.5.1, according to the tar file that I > downloaded > from the Nagios website, the version is supposedly 2.5.2. > > > -----Original Message----- > From: David Gerbec [mailto:[EMAIL PROTECTED] > Sent: Friday, December 29, 2006 9:30 AM > To: Kaplan, Andrew H. > Cc: Andy Shellam (Mailing Lists); Nagios Users mailinglist > Subject: Re: [Nagios-users] Service Check Timed Out Error > > > Hi! > > Kaplan, Andrew H. pravi: >> I ran the chsh command to change the nologin shell for the nagios user to >> /bin/bash, and also provided a password for the nagios account. After that, >> I ran the check_nrpe command again from the command line, ie: manually, and > was >> able to get a response back from the nrpe client. > > If i understand correctly, u ran the plugin su'ed to the nagios user and > the command completed successfully? > > If that's the case, then please check if the xinetd daemon is running > and what the setting for nagios-nrpe are for xinetd. > > What's your NRPE version on the server and the client machine? > > I'm still sure, u got premission problems :o). > > > > > Regards, > D. > >> Listed below are posts that were requested from a previous e-mail: >> >> 1. The output of "check_nrpe -H <nrpe_client> -c <remote_command>" run >> as the Nagios user: >> DISK OK [50534480 kb (99%) free on cosmos2:/database >> >> 2. The Nagios command definition for your check_nrpe command: >> # 'check_nrpe' command definition >> define command{ >> command_name check_nrpe >> command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -t 60 -c $ARG1$ >> >> 3. A Nagios service definition that uses the check_nrpe service on the >> relevant host: >> command[check_disk1]=/usr/local/nagios/libexec/check_disk -w 20% -c 10% -p >> /cosmos2/database >> >> >> >> >> >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of Andy Shellam >> (Mailing Lists) >> Sent: Friday, December 29, 2006 8:58 AM >> To: Kaplan, Andrew H. >> Cc: Nagios Users mailinglist >> Subject: Re: [Nagios-users] Service Check Timed Out Error >> >> Kaplan, Andrew H. wrote: >>> I configured the ip tables on both the nagios server and the nrpe client to >>> allow all inbound and outbound traffic. Additionally, I made sure the >>> /etc/services file on both systems had port 5666 open to tcp and udp >>> traffic. > >>> I was able to telnet to port 5666 on the nrpe client, but I was still >>> getting >> a >>> connection refused for the same port on the server. >>> >> You won't be able to telnet back from the client to the server unless >> you're also running nrpe on the server. >> As long as you can telnet server to client on that port, you're fine. >> >> Also nrpe uses TCP only (I believe.) >>> I verified also, that the network speed, ie: half vs. full duplex, was the >> same >>> for both systems. The speed here is 100 half duplex no autonegotiation. >>> >>> I repeatedly ran the check_nrpe command manually and did get output back > every >>> time. Why am I able to run the command manually, but not automatically? >>> >> Like David says, try su'ing to the Nagios user and running the command >> manually. >> >> If all else fails, please post back the following: >> >> >> 2. The Nagios command definition for your check_nrpe command >> 3. A Nagios service definition that uses the check_nrpe service on the >> relevant host >> >> Andy. >> >> ------------------------------------------------------------------------- >> 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 >> 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 >> >> >> >> >> THE INFORMATION TRANSMITTED IN THIS ELECTRONIC COMMUNICATION IS INTENDED ONLY > FOR THE PERSON OR ENTITY TO WHOM IT IS ADDRESSED AND MAY CONTAIN CONFIDENTIAL > AND/OR PRIVILEGED MATERIAL. ANY REVIEW, RETRANSMISSION, DISSEMINATION OR > OTHER > USE OF OR TAKING OF ANY ACTION IN RELIANCE UPON, THIS INFORMATION BY PERSONS > OR > ENTITIES OTHER THAN THE INTENDED RECIPIENT IS PROHIBITED. IF YOU RECEIVED > THIS > INFORMATION IN ERROR, PLEASE CONTACT THE SENDER AND THE PRIVACY OFFICER, AND > PROPERLY DISPOSE OF THIS INFORMATION. >> >> >> ------------------------------------------------------------------------- >> 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 >> 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 > > > > > > THE INFORMATION TRANSMITTED IN THIS ELECTRONIC COMMUNICATION IS INTENDED ONLY > FOR THE PERSON OR ENTITY TO WHOM IT IS ADDRESSED AND MAY CONTAIN CONFIDENTIAL > AND/OR PRIVILEGED MATERIAL. ANY REVIEW, RETRANSMISSION, DISSEMINATION OR > OTHER USE OF OR TAKING OF ANY ACTION IN RELIANCE UPON, THIS INFORMATION BY > PERSONS OR ENTITIES OTHER THAN THE INTENDED RECIPIENT IS PROHIBITED. IF YOU > RECEIVED THIS INFORMATION IN ERROR, PLEASE CONTACT THE SENDER AND THE PRIVACY > OFFICER, AND PROPERLY DISPOSE OF THIS INFORMATION. > > ------------------------------------------------------------------------- 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 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
