check_http -S through ServerIron fails

Skip Montanaro skip at pobox.com
Fri Jan 9 18:54:27 CET 2004


I've encountered in "interesting" problem with the check_http plugin.  We
have some machines fronted by a Foundry Networks ServerIron switch for load
balancing.  The folks who run the server recently changed to backend server
selection using SSL Session ID.  This hoses check_http (v. 1.36) which now
gets a connect timeout:

    $ /usr/local/nagios/libexec/check_http -S -H 129.105.213.249
    CRITICAL - Socket timeout after 10 seconds

Using check_http v. 1.24 from a different machine seems to work.  It gets a
302 response:

    % ~nagios/libexec/check_http -S -H 129.105.213.249
    HTTP ok: HTTP/1.1 302 Moved Temporarily -   0.384 second response time |time=  0.384

Dispensing with the -S flag also works because the ServerIron is still
selecting a backend server for http based on the IP address:

    $ /usr/local/nagios/libexec/check_http -H 129.105.213.249
    HTTP OK HTTP/1.1 200 OK - 0.006 second response time |time=0.006

How (if at all) can I generate the necessary session id in check_http and
get it to the ServerIron?

Thx,

-- 
Skip Montanaro
Got gigs? http://www.musi-cal.com/submit.html
Got spam? http://spambayes.sf.net/
skip at pobox.com


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
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





More information about the Users mailing list