CRITICAL Socket Timeout Errors When Monitoring HTTP Site

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Brooks
Posts: 36
Joined: Thu Dec 10, 2015 2:29 pm

Re: CRITICAL Socket Timeout Errors When Monitoring HTTP Site

Post by Brooks »

I'm sure the site does have multiple ip addresses. Why if I'm monitoring the url this needs to know an IP address. What is the best way to add this without requiring a specific ip?
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: CRITICAL Socket Timeout Errors When Monitoring HTTP Site

Post by rkennedy »

You'll want to navigate to Configure -> Core Config Manager -> Click 'Services' -> Find the one in question.

Then, remove the -I x.x.x.x part from your check_command. It'll work fine and only use DNS, without validating the IP that DNS returns. The -I is used in conjunction when a specific IP should be returned.

Here's another example -

Code: Select all

[root@localhost libexec]# ./check_http -H google.com -f ok -u "/" -S -p 443
HTTP OK: HTTP/1.1 301 Moved Permanently - 654 bytes in 0.113 second response time |time=0.113418s;;;0.000000 size=654B;;;0
Former Nagios Employee
Brooks
Posts: 36
Joined: Thu Dec 10, 2015 2:29 pm

Re: CRITICAL Socket Timeout Errors When Monitoring HTTP Site

Post by Brooks »

That makes sense. I'll give that a shot.

Thanks
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: CRITICAL Socket Timeout Errors When Monitoring HTTP Site

Post by rkennedy »

Sounds good - let us know if you need any further assistance.
Former Nagios Employee
Locked