check_http -S through ServerIron fails

[Jeff Rodriguez]

It shouldn't be timing out with those options. You don't follow server 
redirections, can you telnet to the virtual ip from the nagios box on 443?

That's what the error below seems to indicate, that you can't.

Just a thought,
Jeff

Skip Montanaro wrote:

>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,
>
>  
>



-------------------------------------------------------
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