Hi.
We have dozens of windows virtual servers monitored via NSClient + +
Only in one server following this message appears with great frequency: CRITICAL - Socket timeout after 10 seconds
I've reinstalled the NSClient + + and apparently the server has no connectivity problem
How can we debug and solve this problem?
Best Regards
Tcp
CRITICAL - Socket timeout after 10 seconds
-
sreinhardt
- -fno-stack-protector
- Posts: 4366
- Joined: Mon Nov 19, 2012 12:10 pm
Re: CRITICAL - Socket timeout after 10 seconds
How long has this windows system been up and running? There is a known bug with windows network stack if the system is up for an extended period of time. Other things you should start with, let's make sure the port is open first.
Code: Select all
nmap -p 5666,12489 [windows 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.
Re: CRITICAL - Socket timeout after 10 seconds
The server is up for 8 days
nmap results below
Starting Nmap 5.51 ( http://nmap.org ) at 2014-08-04 14:39 BRT
Nmap scan report for XXXXX (XXX.XXX.X.XXX)
Host is up (0.00038s latency).
PORT STATE SERVICE
5666/tcp filtered nrpe
12489/tcp filtered unknown
MAC Address: XXXXXXXXXXX (Unknown)
Nmap done: 1 IP address (1 host up) scanned in 1.41 seconds
nmap results below
Starting Nmap 5.51 ( http://nmap.org ) at 2014-08-04 14:39 BRT
Nmap scan report for XXXXX (XXX.XXX.X.XXX)
Host is up (0.00038s latency).
PORT STATE SERVICE
5666/tcp filtered nrpe
12489/tcp filtered unknown
MAC Address: XXXXXXXXXXX (Unknown)
Nmap done: 1 IP address (1 host up) scanned in 1.41 seconds
Re: CRITICAL - Socket timeout after 10 seconds
Both ports that you need open (12489 and 5666) are filtered...
You will need to modify your firewall rules and open these ports.5666/tcp filtered nrpe
12489/tcp filtered unknown
Be sure to check out our Knowledgebase for helpful articles and solutions!