Is it a virtual server?
I had got the same issue once, when I used Nagios running on a VmWare machine.
As soon as I migrated it to HyperV, everything started working.
CRITICAL - Socket timeout after 20 seconds
-
DiegoAnjos
- Posts: 49
- Joined: Thu Feb 14, 2013 9:32 am
-
sreinhardt
- -fno-stack-protector
- Posts: 4366
- Joined: Mon Nov 19, 2012 12:10 pm
Re: CRITICAL - Socket timeout after 20 seconds
Well, I wouldn't put it on the hypervisor right away, that's not a terribly common problem. Let's start by making sure those ports opened up with the previous changes.
Code: Select all
nmap -p 5666,12489 [hostname\IP]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.
-
lafargeuser
- Posts: 341
- Joined: Thu Sep 27, 2012 12:23 am
Re: CRITICAL - Socket timeout after 20 seconds
# nmap -p 5666,12489 172.17.85.69
Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2014-01-17 11:04 IST
Interesting ports on BGLRLXNAGIOS01.BGLRGOC.COM (172.16.98.129):
PORT STATE SERVICE
5666/tcp open unknown
12489/tcp closed unknown
Nmap finished: 1 IP address (1 host up) scanned in 0.012 seconds
Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2014-01-17 11:04 IST
Interesting ports on BGLRLXNAGIOS01.BGLRGOC.COM (172.16.98.129):
PORT STATE SERVICE
5666/tcp open unknown
12489/tcp closed unknown
Nmap finished: 1 IP address (1 host up) scanned in 0.012 seconds
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: CRITICAL - Socket timeout after 20 seconds
Alright, so it looks like currently the port used by check_nt is closed, while the NRPE port "5666" is open, do you have networking equipment in the route to the windows server, or the servers that are displaying this? Did you check the windows firewall?
-
lafargeuser
- Posts: 341
- Joined: Thu Sep 27, 2012 12:23 am
Re: CRITICAL - Socket timeout after 20 seconds
So for working alright. But from last couple of days I am facing this issue.
Windows firewall is off.
Windows firewall is off.
Re: CRITICAL - Socket timeout after 20 seconds
Can you post your nsclient config in code wraps?
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.
-
lafargeuser
- Posts: 341
- Joined: Thu Sep 27, 2012 12:23 am
Re: CRITICAL - Socket timeout after 20 seconds
Attaching....
- Attachments
-
NSC.ini- Conf file
- (12.86 KiB) Downloaded 676 times
Re: CRITICAL - Socket timeout after 20 seconds
Something is very strange here. Is 172.16.98.129 your windows server? I ask because port 5666 was open while 12489 was not in your previous nmap, but your nsclient config is not configured for nrpe(5666), but is for check_nt(12489). Are you sure this is the file from the windows system and that the the windows ip is 172.16.98.129?
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.
-
lafargeuser
- Posts: 341
- Joined: Thu Sep 27, 2012 12:23 am
Re: CRITICAL - Socket timeout after 20 seconds
172.16.98.129 is (Nagios Server)
However, I have changed this to 192.168.
However, I have changed this to 192.168.
Re: CRITICAL - Socket timeout after 20 seconds
What is the windows server ip?
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.