FedoraThis forum is for the discussion of the Fedora Project.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
We have a server running Fedora Core 3 and I have modified the /etc/services file to open port 5666 to allow TCP connections. The syntax of the newly added line is as follows:
nrpe 5666/tcp # NRPE
After the line was added I stopped and restarted xineted via the startup script /etc/init.d/xinetd. After that, I tested the port's accessibility via telnet from a Windows 2000 workstation. The command syntax used there was:
telnet <hostname> 5666
The result was an error message saying connection could not be established. I verified the system could be pinged and also was found via nslookup.
What else do I need to check for in order to correct this problem? Thanks.
I don't know how nrpe would be started exactly, but editing the /etc/services file would not start it. See if there is an nrpe startup file in /etc/init.d . An example might be /etc/init.d/nrpe start . You can look to see what services are actively listening on ports by using this command: netstat -pantu
Also, if it is running you may need to allow that port to be let through your firewall. Do you have a firewall running right now?
Last edited by benjithegreat98; 04-25-2005 at 01:54 PM.
< I don't know how nrpe would be started exactly, but editing the /etc/services file would not start it. See if there is an nrpe startup file in < /etc/init.d . An example might be /etc/init.d/nrpe start .
The nrpe client is normally started via a script in the /etc/xinetd.d directory. The syntax of the script is the following:
flags = REUSE
socket_type = STREAM
wait = no
user = root
server = /usr/local/nagios/bin/nrpe
server_args = -c /usr/local/nagios/etc/nrpe.cfg --inetd
log_on_failure += USERID
disable = no
only_from = < ip address >
The permissions for the file itself are: -rw-r--r-- 1 root root 311 <date> nrpe
< You can look to see what services are actively listening on ports by using this command: netstat -pantu
The results of the above command indicated that the 5666 port is not being actively listened upon.
< Also, if it is running you may need to allow that port to be let through your firewall. Do you have a firewall running right now?
I ran the setup command within xterm and checked the status of the firewall. The utility indicated the firewall was disabled.
I was curious and installed the rpms to nrpe..... It installed a startup file called /etc/init.d/nrpe . Do you have that file? You could disable the xinit version of nrpe and just call /etc/init.d/nrpe start to get it started. Do you have a file called /etc/init.d/nrpe ?
First off -- Thank-you for your replies to my e-mail. I tried a different tact where instead of using the xinetd approach to starting the file, I had the file activated into "daemon" mode via /etc/rc.local. That appears to have solved the problem. I'm sorry I had not replied sooner to your responses.
Second -- The question was asked: what is nrpe for? Simply put, it is the client program or agent that is installed on remote computers that allow the Nagios server to send requests to the remote systems and get responses. The NRPE program can be configured to poll the
client system for things like disk usage, cpu load, and so on. If you have any other questions, let me know.