Service Status Crticial after Client Install
Re: Service Status Crticial after Client Install
Output:
[root@istation libexec]# /usr/local/nagios/libexec/check_nrpe -H 168.25.19.110 -n nmap 168.25.19.110 -p 5666
CHECK_NRPE: Socket timeout after 10 seconds.
[root@istation libexec]# /usr/local/nagios/libexec/check_nrpe -H 168.25.19.110 -n nmap 168.25.19.110 -p 5666
CHECK_NRPE: Socket timeout after 10 seconds.
Re: Service Status Crticial after Client Install
We are asking you to run two separate commands and you have put them all on one line.
In your Nagios XI server's terminal, type out the following on the command line:
Then press the Enter key.
Then type this out in the same terminal:
and press the Enter key again.
Once you have done these two things, copy the output and paste the results here.
In your Nagios XI server's terminal, type out the following on the command line:
Code: Select all
/usr/local/nagios/libexec/check_nrpe -H 168.25.19.110 -nThen type this out in the same terminal:
Code: Select all
nmap 168.25.19.110 -p 5666Once you have done these two things, copy the output and paste the results here.
Former Nagios employee
Re: Service Status Crticial after Client Install
Thank you for clarifying.
On the first command:
[root@istation ~]# /usr/local/nagios/libexec/check_nrpe -H 168.25.19.110 -n
CHECK_NRPE: Socket timeout after 10 seconds.
On the second command:
[root@istation ~]# nmap 168.25.19.110 -p 5666
Starting Nmap 5.51 ( http://nmap.org ) at 2014-04-25 14:54 UTC
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.07 seconds
[root@istation ~]#
On the first command:
[root@istation ~]# /usr/local/nagios/libexec/check_nrpe -H 168.25.19.110 -n
CHECK_NRPE: Socket timeout after 10 seconds.
On the second command:
[root@istation ~]# nmap 168.25.19.110 -p 5666
Starting Nmap 5.51 ( http://nmap.org ) at 2014-04-25 14:54 UTC
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.07 seconds
[root@istation ~]#
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: Service Status Crticial after Client Install
Looks like whatever system is attached to that address is either down, or blocking attempts to see its status, as nmap says. You will need to figure this out before we help you further on the Nagios related end of things.
Re: Service Status Crticial after Client Install
I think I listed the incorrect IP address for the server. As the server is not down. The server in question has an internal and external IP and I was listing the external. So I tried the commands again with the other IP address and got the following.
1st command:
[root@istation ~]# /usr/local/nagios/libexec/check_nrpe -H 10.4.10.110 -n
CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.
2nd command:
[root@istation ~]# nmap 10.4.10.110 -p 5666
Starting Nmap 5.51 ( http://nmap.org ) at 2014-04-25 16:46 UTC
Nmap scan report for 10.4.10.110
Host is up (0.00023s latency).
PORT STATE SERVICE
5666/tcp open nrpe
MAC Address: 00:50:56:02:00:55 (VMware)
Nmap done: 1 IP address (1 host up) scanned in 0.19 seconds
What does this tell you?
Thank you!
Constance
1st command:
[root@istation ~]# /usr/local/nagios/libexec/check_nrpe -H 10.4.10.110 -n
CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.
2nd command:
[root@istation ~]# nmap 10.4.10.110 -p 5666
Starting Nmap 5.51 ( http://nmap.org ) at 2014-04-25 16:46 UTC
Nmap scan report for 10.4.10.110
Host is up (0.00023s latency).
PORT STATE SERVICE
5666/tcp open nrpe
MAC Address: 00:50:56:02:00:55 (VMware)
Nmap done: 1 IP address (1 host up) scanned in 0.19 seconds
What does this tell you?
Thank you!
Constance
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: Service Status Crticial after Client Install
Okay, so we have the correct address now. So lets try running that command again, without '-n':
Code: Select all
/usr/local/nagios/libexec/check_nrpe -H 10.4.10.110Re: Service Status Crticial after Client Install
Sorry for that mix up.
Here's the results of the new command:
[root@istation ~]# /usr/local/nagios/libexec/check_nrpe -H 10.4.10.110
CHECK_NRPE: Error - Could not complete SSL handshake.
I followed the instructions on Nagios for installing the client agent on the server to be monitored to the letter, but could there be something else I may have missed?
This is a CAS (Central Authentication Service) server if that makes a difference.
Thank you,
Constance
Here's the results of the new command:
[root@istation ~]# /usr/local/nagios/libexec/check_nrpe -H 10.4.10.110
CHECK_NRPE: Error - Could not complete SSL handshake.
I followed the instructions on Nagios for installing the client agent on the server to be monitored to the letter, but could there be something else I may have missed?
This is a CAS (Central Authentication Service) server if that makes a difference.
Thank you,
Constance
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: Service Status Crticial after Client Install
Okay, can you upload your nrpe.cfg or xinetd nrpe config if you are using xinetd from the remote host? And let us know what your XI server's address is?
Code: Select all
/usr/local/nagios/etc/nrpe.cfg
/etc/xinetd.d/nrpe.cfgRe: Service Status Crticial after Client Install
Both are attached. However, the site would not let me attach the nrpe file from the /etc/ directory due to the file extension, so I made it a .txt file.
Thank you!
Thank you!
You do not have the required permissions to view the files attached to this post.
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: Service Status Crticial after Client Install
You need to add the XI server's address in the allowed_hosts section. It looks like you may be using xinetd as there is a config file for NRPE there, so make this change on the only_from line, you should separate 127.0.0.1 and your XI server's address with one space. Once you have added the xi server's address, restart xinetd:
Code: Select all
service xinetd restart