Problems with XI not seeing HTTP hosts (down)

[dlukinski]

Hello XI Support

We've suddenly developed problems with otherwise healthy monitoring of some HTTP hosts (picture attached)
Most of these are HTTP-availability configured, but down as far as Nagios XI concerned. (CRITICAL - Socket timeout after 10 seconds)

all the hosts listed are actually online and accessible

How to resolve this problem?

[rkennedy]

I ran a test on my end against one of the hosts listed, and even here it took 5 seconds to finish -

Code: Select all

[root@centos7x64 libexec]# ./check_http -H outlook.office.com
HTTP OK: HTTP/1.1 301 Moved Permanently - 481 bytes in 5.161 second response time |time=5.160872s;;;0.000000 size=481B;;;0

Depending on the load / network of your machine, I could see it taking longer than 10 seconds to finish up with what I mentioned above. Can you try appending -t 30 to the end of them?

If that doesn't work, could you post the full output with a -v? Here's it ran on my end -

Code: Select all

[root@centos7x64 libexec]# ./check_http -H outlook.office.com -t 30 -v
GET / HTTP/1.1
User-Agent: check_http/v2.0.3 (nagios-plugins 2.0.3)
Connection: close
Host: outlook.office.com
Accept: */*


http://outlook.office.com:80/ is 481 characters
STATUS: HTTP/1.1 301 Moved Permanently
**** HEADER ****
Cache-Control: no-cache
Pragma: no-cache
Content-Length: 0
Location: https://outlook.office.com/owa/
Server: Microsoft-IIS/8.5
X-FEServer: DM5PR18CA0016
X-RequestId: 5047a022-a236-48ec-8d90-a5bfd208bf49
X-Powered-By: ASP.NET
X-FEServer: DM5PR18CA0016
X-MSEdge-Ref: Ref A: 4CC104DE747547A69B27A81AA9B61D39 Ref B: 351D0AAA01CD0B7BE150F83AE0A9C278 Ref C: Thu Jan 12 07:51:03 2017 PST
Date: Thu, 12 Jan 2017 15:51:03 GMT
Connection: close
**** CONTENT ****

HTTP OK: HTTP/1.1 301 Moved Permanently - 481 bytes in 5.146 second response time |time=5.146166s;;;0.000000 size=481B;;;0

[dlukinski]

I ran a test on my end against one of the hosts listed, and even here it took 5 seconds to finish -

Code: Select all

[root@centos7x64 libexec]# ./check_http -H outlook.office.com
HTTP OK: HTTP/1.1 301 Moved Permanently - 481 bytes in 5.161 second response time |time=5.160872s;;;0.000000 size=481B;;;0

Depending on the load / network of your machine, I could see it taking longer than 10 seconds to finish up with what I mentioned above. Can you try appending -t 30 to the end of them?

If that doesn't work, could you post the full output with a -v? Here's it ran on my end -

Code: Select all

[root@centos7x64 libexec]# ./check_http -H outlook.office.com -t 30 -v
GET / HTTP/1.1
User-Agent: check_http/v2.0.3 (nagios-plugins 2.0.3)
Connection: close
Host: outlook.office.com
Accept: */*


http://outlook.office.com:80/ is 481 characters
STATUS: HTTP/1.1 301 Moved Permanently
**** HEADER ****
Cache-Control: no-cache
Pragma: no-cache
Content-Length: 0
Location: https://outlook.office.com/owa/
Server: Microsoft-IIS/8.5
X-FEServer: DM5PR18CA0016
X-RequestId: 5047a022-a236-48ec-8d90-a5bfd208bf49
X-Powered-By: ASP.NET
X-FEServer: DM5PR18CA0016
X-MSEdge-Ref: Ref A: 4CC104DE747547A69B27A81AA9B61D39 Ref B: 351D0AAA01CD0B7BE150F83AE0A9C278 Ref C: Thu Jan 12 07:51:03 2017 PST
Date: Thu, 12 Jan 2017 15:51:03 GMT
Connection: close
**** CONTENT ****

HTTP OK: HTTP/1.1 301 Moved Permanently - 481 bytes in 5.146 second response time |time=5.146166s;;;0.000000 size=481B;;;0

Please close. I googled lots that day, but it was not the case: slow VMWARE Nagios XI VM migration/move cause this behaviour (we run Nagios on 3rd party VMWARE cluster).

[rkennedy]

Ah! Glad to hear you were able to find a logical answer for it.

/closed