Special check_http variation

[Matthias Eichler]

Hi Karl,

I can increase the timeout as much as I want, it will always bring an
timeout here.
Especially because it does not take so long to get the URL, with telnet
it takes as long as you need to type "get /cgi-bin/image" and with a
browser you get the picture back immediately...

Matthias

On Wed, 2003-05-14 at 12:48, Karl DeBisschop wrote:
> On Wed, 2003-05-14 at 05:25, Matthias Eichler wrote:
> > Hi List,
> > 
> > we have some special software running which gives some jpeg and
> > motion-jpeg output of some videostream. Unfortunately this software
> > is not very stable, so I wanted to monitor it with check_http.
> > 
> > The image can be downloaded via http://195.30.64.242/cgi-bin/image.
> > The motion jpeg stream can be get as an octet-stream via
> > http://195.30.64.242/cgi-bin/video.
> > 
> > The command "./check_http -I 195.30.64.242" brings the correct 404 page,
> > because there is no directory index.
> > The command "./check_http -I 195.30.64.242 -u /cgi-bin/image" brings a
> > timeout after 10 seconds, although I can telnet to that address and can
> > download the image via "GET /cgi-bin/image".
> > 
> > Can anybody give us some hint?!?
> > Would be great and feel free to try the URL...
> 
> It took far more than 10 seconds on my end -- maybe you just need to use
> the timeout option? (-t or --timeout, as always, just look at the plugin
> help listing)
> 
> --
> Karl
> 
> > Thanks,
> > 
> > Matthias Eichler
-- 
Matthias Eichler <mylists at ame.de>
AME Aigner Media & Entertainment



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
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