CRITICAL - Socket timeout after 10 seconds

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
npolovenko
Support Tech
Posts: 3457
Joined: Mon May 15, 2017 5:00 pm

Re: CRITICAL - Socket timeout after 10 seconds

Post by npolovenko »

@andrewatmacys, Please send in your Nagios XI System Profile indicating the name of the host, and the name of the service.
To send us your system profile. Login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and upload it to a cloud storage of your choice. You can share a link with me in a personal message.
After you upload the profile please post something in this thread to bring it up in the support queue.

Profile was recieved and shared with the support team
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
andrewatmacys
Posts: 114
Joined: Tue Feb 06, 2018 9:25 am

Re: CRITICAL - Socket timeout after 10 seconds

Post by andrewatmacys »

I have sent you a PM. Please let me know if the file gets to you, I didn't see your comment about cloud services before I sent it.
npolovenko
Support Tech
Posts: 3457
Joined: Mon May 15, 2017 5:00 pm

Re: CRITICAL - Socket timeout after 10 seconds

Post by npolovenko »

@andrewatmacys, That also works. Please run the following commands from the command line and provide the output:

Code: Select all

/usr/local/nagios/libexec/check_http -f ok -I 11.xx.xx.xx -u '/' -S -p 443 -a 'term1:term2'
/usr/local/nagios/libexec/check_http -f ok -H 11.xx.xx.xx -u '/' -S -p 443 
ping 11.xx.xx.xx
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
andrewatmacys
Posts: 114
Joined: Tue Feb 06, 2018 9:25 am

Re: CRITICAL - Socket timeout after 10 seconds

Post by andrewatmacys »

I will, can you edit the text in the quotes to say term1:term2 in the above reply?
npolovenko
Support Tech
Posts: 3457
Joined: Mon May 15, 2017 5:00 pm

Re: CRITICAL - Socket timeout after 10 seconds

Post by npolovenko »

@andrewatmacys, Changed it. Sorry for that.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
andrewatmacys
Posts: 114
Joined: Tue Feb 06, 2018 9:25 am

Re: CRITICAL - Socket timeout after 10 seconds

Post by andrewatmacys »

[nagios@esu2v236 ~]$ sudo /usr/local/nagios/libexec/check_http -f ok -I 11.xx.xx.xx -u '/' -S -p 443 -a 'term1:term2'
connect to address 11.xx.xx.xx and port 443: Connection refused
HTTP CRITICAL - Unable to open TCP socket

[nagios@esu2v236 ~]$ /usr/local/nagios/libexec/check_http -f ok -I 11.xx.xx.xx -u '/' -S -p 443
connect to address 11.xx.xx.xx and port 443: Connection refused
HTTP CRITICAL - Unable to open TCP socket

[b005407@esu2v236 ~]$ ping 11.xx.xx.xx
PING 11.xx.xx.xx (11.xx.xx.xx) 56(84) bytes of data.
64 bytes from 11.xx.xx.xx: icmp_seq=1 ttl=255 time=1.70 ms
64 bytes from 11.xx.xx.xx: icmp_seq=2 ttl=255 time=33.2 ms
64 bytes from 11.xx.xx.xx: icmp_seq=3 ttl=255 time=1.42 ms
64 bytes from 11.xx.xx.xx: icmp_seq=4 ttl=255 time=15.1 ms
64 bytes from 11.xx.xx.xx: icmp_seq=5 ttl=255 time=2.60 ms
64 bytes from 11.xx.xx.xx: icmp_seq=6 ttl=255 time=43.7 ms
64 bytes from 11.xx.xx.xx: icmp_seq=7 ttl=255 time=5.19 ms
^C
--- 11.xx.xx.xx ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6471ms
rtt min/avg/max/mdev = 1.420/14.705/43.720/15.887 ms
npolovenko
Support Tech
Posts: 3457
Joined: Mon May 15, 2017 5:00 pm

Re: CRITICAL - Socket timeout after 10 seconds

Post by npolovenko »

@andrewatmacys, I wonder if the SSL port is closed. Please run:

Code: Select all

nmap -p 443 11.xx.xx.xx
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
andrewatmacys
Posts: 114
Joined: Tue Feb 06, 2018 9:25 am

Re: CRITICAL - Socket timeout after 10 seconds

Post by andrewatmacys »

Reported that host was down, but tried suggestion to use -Pn

Starting Nmap 6.47 ( http://nmap.org ) at 2018-04-27 13:14 EDT
Strange error from connect (22):Invalid argument
Nmap scan report for 443 (0.0.1.187)
Host is up.
All 1000 scanned ports on 443 (0.0.1.187) are filtered

Nmap scan report for 11.xx.xx.xx
Host is up.
All 1000 scanned ports on 11.xx.xx.xx are filtered

Nmap done: 2 IP addresses (2 hosts up) scanned in 0.10 seconds
npolovenko
Support Tech
Posts: 3457
Joined: Mon May 15, 2017 5:00 pm

Re: CRITICAL - Socket timeout after 10 seconds

Post by npolovenko »

@andrewatmacys, Filtered means your ports are behind the firewall. You need to disable the firewall or add a rule to open the port 443.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Locked