Basic Nagios Check_http question

[Marc Powell]

> -----Original Message-----
> From: Larry Crowder [mailto:CrowderLG at ldschurch.org]
> Sent: Thursday, October 09, 2003 12:15 PM
> To: nagios-users at lists.sourceforge.net
> 
> 
> Note that I have tried using different users for authentication (even
> root).  I have also tried using the other web pages that come with
Nagios.
> I am confident that there is just something simple (dumb)  I am not
> thinking of.
> 
> Any ideas?
> 
> Larry C
> 
> (Command I use.  This is on the Nagios server and checks the Nagios
> main.html on its own directory structure.  I use a real IP address but
use
> localhost here)
> ./check_http -H localhost  -a nagios:nagios -u
> /usr/local/nagios/share/main.html
> (Results)
> HTTP WARNING: HTTP/1.1 404 Not Found
> 
> (I checked with ls to make sure I was looking in the right directory)
> 
> ls /usr/local/nagios/share
> contexthelp  docs  images  index.html  main.html  media  robots.txt
> side.html  ssi  stylesheets

Your apache error logs would probably point this out but it's going to
be looking for something like
http://localhost/usr/local/nagios/share/main.html, which unless you've
done something really strange with your apache config isn't going to
work. You probably want something more like --

./check_http -H localhost -a nagios:nagios -u /main.html

Also, if you're not using name based vhosts, then you should use the -I
option instead of -H.

./check_http --help for more.

--
Marc 


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
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