Basic Nagios Check_http question

[Larry Crowder]

Hello,
 
I have checked quite a bit in the Nagios list, but still cannot understand why I am having this problem with check_http.  ( I am experimenting to get it to work)
 
I have a single Redhat Linux 9 installation .  I just want to check the Nagios main.html page to test the plugin out.    After narrowing the syntax down from examples I have seen in the Nagios List, I am confused as to why I keep getting "Not Found" with check_http.  
 
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


Larry 


------------------------------------------------------------------------------
This message may contain confidential information, and is intended only for the use of the individual(s) to whom it is addressed.


==============================================================================



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