Service Status Crticial after Client Install

[Constance]

After making the modifications and upon entering the restart command (service xinted restart) I received the following error, so I changed directory and still got the same error below:

[root@istation etc]# service xinted restart
xinted: unrecognized service

[root@istation xinetd.d]# service xinted restart
xinted: unrecognized service

Also, just to confirm that I placed my IP address in the proper places.....

In /etc/xinetd.d/ I modified the nrpe.cfg file to add the IP address (one space apart) from the 127.0.0.1 on the 'only_from' line. **Copy of modified file attached.

Then in netd.d/ I modified the nrpe file to have the IP address in the allowed_hosts area one space apart from the 127.0.0.1. **Copy of modified file attached.

Since the restart command did not work for xinted should I modify the nrpe.cfg file area of 'Server address'? See attached file.

Thank you!
Constance

[slansing]

You need to restart xinetd, it is the name of the service who's nrpe configuration you just changed above.

Code: Select all

service xinetd restart

[Constance]

Okay - I've restarted xinetd.
However, when I try to re-schedule nagios to check that server again it doesn't seem to take my request.

How can I get nagios to recheck that server?

Thanks!

[lmiltchev]

However, when I try to re-schedule nagios to check that server again it doesn't seem to take my request.

Can you elaborate on this? What happens when you click on the "Schedule an immediate check" quick actions button?
What is the check that is failing? Can you run it from the CLI and show us the exact command along with the output of it?

[Constance]

So sorry for the late response. Thank you for writing 'lmiltchev'.

Can you elaborate on this? What happens when you click on the "Schedule an immediate check" quick actions button?

A pop-up box appears that shows the command went through successfully and then it disappears.

What is the check that is failing?

Please see the screen shot image attached (Service-Error-Status) for each service that is showing critical. The status information has not changed from what it showed at the beginning of this thread.
I've also attached a screen shot image of the services that are now considered 'ok'.

Can you run it from the CLI and show us the exact command along with the output of it?

I'm not sure what the 'CLI' is - command line interface ?
The scheduling of a status check I do via the web interface. Please see the screen shot attached 'Next-Status-Check'.
Even though I clicked on the 'Schedule an immediate check' action it scheduled the check for an hour out and I'm currently waiting on that report.
The previous checks have all continued to show the same results as those I've attached for review.

I appreciate everyone's help and suggestions and hope we can find a resolution.

Thank you,
Constance

[lmiltchev]

Run the following commands and show us the output:

On the client (remote machine):

Code: Select all

grep "only_from" /etc/xinetd.d/nrpe
service xinetd restart

On the Nagios XI server:

Code: Select all

ifconfig
/usr/local/nagios/libexec/check_nrpe -H 10.4.10.110

[Constance]

For the remote client:

[cas@mydsccas ~]$ grep "only_from" /etc/xinetd.d/nrpe
only_from = 168.25.19.112
[root@mydsccas ~]# service xinetd restart
Stopping xinetd: [ OK ]
Starting xinetd: [ OK ]

On the Nagios XI Server:

[root@istation ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:50:56:02:00:12
inet addr:10.4.10.112 Bcast:10.4.10.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fe02:12/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:609894 errors:0 dropped:0 overruns:0 frame:0
TX packets:434929 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:470854621 (449.0 MiB) TX bytes:64508084 (61.5 MiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4735242 errors:0 dropped:0 overruns:0 frame:0
TX packets:4735242 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1806362721 (1.6 GiB) TX bytes:1806362721 (1.6 GiB)

[root@istation ~]# /usr/local/nagios/libexec/check_nrpe -H 10.4.10.110
CHECK_NRPE: Error - Could not complete SSL handshake.
[root@istation ~]# /usr/local/nagios/libexec/check_nrpe -H 168.25.19.110
CHECK_NRPE: Socket timeout after 10 seconds.
[root@istation ~]#

At the beginning of this thread the issue appeared to be with the IP address (168.25.19.110) for the remote server. This server has two IP addresses (168.25.19.110 and 10.4.10.110) an internal and external. SSH works off the 168.25.19.110, which is why I tried using it with Nagios at the beginning. But when I ran into these same errors - I changed the IP over to 10.4.10.110 and the service check for pinging with Nagios worked, but the rest of the services continued to show the 'critical' errors.

[lmiltchev]

The IP of your Nagios XI server is: 10.4.10.112. However, in the "only_from" line in the "/etc/xinetd.d/nrpe" on the client you have "168.25.19.112", which is NOT the Nagios IX server's IP... Please, add the "10.4.10.112" to this line, and restart xinetd.

[scottwilkerson]

I would change the following line

Code: Select all

only_from = 168.25.19.112

to

Code: Select all

only_from = 168.25.19.112 10.4.10.112

then

Code: Select all

service xinetd restart

Now from the XI Server

Code: Select all

/usr/local/nagios/libexec/check_nrpe -H 10.4.10.110

[Constance]

Thank you both very much and thank you Scott Wilkerson for the break down.
I have did as you both mentioned:

For the Remote Client after making the changes the restart output is:
[root@mydsccas xinetd.d]# service xinetd restart
Stopping xinetd: [ OK ]
Starting xinetd: [ OK ]

For the Nagios XI server - I went ahead and restarted xinetd and then ran the check command:
[root@istation xinetd.d]# service xinetd restart
Stopping xinetd: [ OK ]
Starting xinetd: [ OK ]
[root@istation xinetd.d]# /usr/local/nagios/libexec/check_nrpe -H 10.4.10.110
NRPE v2.14

Attached are new screen shots and I've scheduled a new check that will take place in one hour.....However, this is exciting as the service status' are already showing 'ok' for almost all of the services!
There is only one critical showing for "NRPE: Unable to read output" and one warning showing for "Yum Warning: O/S requires an update.".