Well, you have a networking problem. Is the nagios server on the same subnet as your workstation?ofadl wrote:i ran the ping 10.200.50.76 and didint get a reply
Check Windows Processes
Re: Check Windows Processes
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Re: Check Windows Processes
what do u mean by that?
Re: Check Windows Processes
Given your subnet mask, you most likely cannot talk to the 10.200.50.x subnet. You will need to contact a sysadmin to get a new route added to the router at 10.200.40.1 to route to the 10.200.50.x subnet. This is not something we can do for you. You will have to resolve the networking issues with your admins.ofadl wrote:0.0.0.0 10.200.40.1 0.0.0.0 UG 100 0 0 eth0
10.200.40.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Re: Check Windows Processes
so i just spoke with my boss about the networking issue, and he confirmed its not a problem with the network. We tried :
telnet 10.200.50.176 5666
and it worked fine
telnet 10.200.50.176 5666
and it worked fine
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: Check Windows Processes
It looks like "10.200.50.76" is the IP we've been trying.. is 10.200.50.176 the actual IP now?
Re: Check Windows Processes
oh wow, i am so sorry, that was my mistake.. the ip all along was 10.200.50.176 i apoligze. But even when i try to run a check_nrpe on that server, im getting a socket timeout after 10 seconds for check_nrpe
-
sreinhardt
- -fno-stack-protector
- Posts: 4366
- Joined: Mon Nov 19, 2012 12:10 pm
Re: Check Windows Processes
We can try a couple things:
Also try an nmap just to be sure from nagios that there are no issues.
Your result should look something like:
Code: Select all
check_nrpe -H 10.200.50.176 -p 5666 -t 30Code: Select all
nmap -p 5666 10.200.50.176Code: Select all
Starting Nmap 5.51 ( http://nmap.org ) at 2013-07-02 13:13 CDT
Nmap scan report for localhost (127.0.0.1)
Host is up (0.000045s latency).
PORT STATE SERVICE
5666/tcp open nrpeNagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
Re: Check Windows Processes
ok i ran the first command, and that increased the timeout to 30 seconds, then ran:
nmap -p 5666 10.200.50.176
and got :
Starting Nmap 5.21 ( http://nmap.org ) at 2013-07-02 14:43 EDT
Nmap scan report for vnadat121.and.comtexnews.net (10.200.50.176)
Host is up (0.00091s latency).
PORT STATE SERVICE
5666/tcp open nrpe
Nmap done: 1 IP address (1 host up) scanned in 0.11 seconds
nmap -p 5666 10.200.50.176
and got :
Starting Nmap 5.21 ( http://nmap.org ) at 2013-07-02 14:43 EDT
Nmap scan report for vnadat121.and.comtexnews.net (10.200.50.176)
Host is up (0.00091s latency).
PORT STATE SERVICE
5666/tcp open nrpe
Nmap done: 1 IP address (1 host up) scanned in 0.11 seconds
-
sreinhardt
- -fno-stack-protector
- Posts: 4366
- Joined: Mon Nov 19, 2012 12:10 pm
Re: Check Windows Processes
OK so you have definitely confirmed the connection is open and responding. What was returned from the first command, hopefully the remove nrpe servers version?
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
Re: Check Windows Processes
yes the connection is open and responding. The first command:
check_nrpe -H 10.200.50.176 -p 5666 -t 30
returns as follows:
CHECK_NRPE: Socket timeout after 30 seconds.
check_nrpe -H 10.200.50.176 -p 5666 -t 30
returns as follows:
CHECK_NRPE: Socket timeout after 30 seconds.