CRITICAL Socket Timeout Errors When Monitoring HTTP Site
Re: CRITICAL Socket Timeout Errors When Monitoring HTTP Site
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?
Re: CRITICAL Socket Timeout Errors When Monitoring HTTP Site
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 -
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
Re: CRITICAL Socket Timeout Errors When Monitoring HTTP Site
That makes sense. I'll give that a shot.
Thanks
Thanks
Re: CRITICAL Socket Timeout Errors When Monitoring HTTP Site
Sounds good - let us know if you need any further assistance.
Former Nagios Employee