I’ve recently configured an active check with check_htttp (Check HTTP Service), and it is listed fine with the host in Services list. But the status is always critical with this message “CRITICAL - Socket timeout after 10 seconds”. I’ve tried increasing timeout with no luck, and the site is loading fine for me here.
I’ve then tried to run the check_http directly via command line, which was successfull:
./lib/nagios/plugins/check_http -H DOMAIN
HTTP OK: HTTP/1.1 301 Moved Permanently - 609 bytes in 1.137 second response time |time=1.136500s;;;0.000000;10.000000 size=609B;;;0
The check is successful on command line, but WATO always shows this check as CRIT. I’m currently stuck at this position, so any help would be appreciated!
When I attach this rule to localhost server (WATO server) in Explicit hosts, it works fine under it. If I attach it to other hosts in my system, it shows as CRIT.
Any idea?
I actually looking to attach all these check_http active checks under a single HOST other than localhost server. Is it possible?
And my service looks like this: (Here bla is a dummy host with no IP but similar way can you add this host with any attribute and link this active check to it)
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact @fayepal if you think this should be re-opened.