Jason A. Kates skrev: > I am having an issue with nagios checking our HP ILO consoles. > > With the old firmware the checks worked fine. We have now upgraded the > consoles to "iLO 2 Firmware Version: 1.61 08/31/2008". > > I am able to test if the consoles are responding via wget & curl, > check_http used to work but no longer works. One think that I did > notice in my testing is that the embedded web server only supports > HTTP/1.1 in the old version HTTP/1.0 was supported. > > > This is the post upgrade results: > ./nagios/libexec/check_http -S -H 10.40.31.81 -t 20 > CRITICAL - Socket timeout after 20 seconds If you add option -N to the arguments it will work. it's an issue i have seen with check_http and HTTP/1.1
i think op5 have sent a patch for upstream about this (will check with our devel team) > > > Interestingly this works: > ./nagios/libexec/check_http -S -H 10.40.31.81 -C7 -t 20 > OK - Certificate will expire on 05/22/2013 05:12. > > > Idea's for fixes or ways to debug this would be appreciated. I rather > not move the test to perl, wget or curl as I currently use the data > results with nagios grapher to create response time graphs. > > Thanks in advance -Jason > > check_http v2053 (nagios-plugins 1.4.13) > -- Vänliga hälsningar / Best Regards Mattias Ryrlén __________________________ op5 AB Första Långgatan 19 SE-413 27 Göteborg Mobil: +46 735-17 70 99 Support: +46 31-774 09 24 www.op5.com ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
