CGI Error

[Josh]

OK.  I know this must be a common error but I can't
find a solution for my situation anywhere online,
FAQs, or forums.

Here's the error I get when clicking on one of the
CGIs on the left frame of the web interface:

----
Whoops!
Error: Could not read object configuration data!

Here are some things you should check in order to
resolve this error: 


Verify configuration options using the -v command-line
option to check for errors. 
Check the Nagios log file for messages relating to
startup or status data errors. 
Make sure you've compiled the main program and the
CGIs to use the same object data storage options (i.e.
default text file or template-based file). 
----

Here's how I configured nagios-2.0b3:

./configure \
  --prefix=/usr/local/nagios-2.0b3 \
  --with-lockfile=/var/lock/subsys/nagios \
  --with-nagios-user=nagios \
  --with-nagios-grp=nagios \
  --with-perlcache \
  --enable-embedded-perl \
  --with-gd-inc=/usr/local/include \
  --with-gd-lib=/usr/local/lib \
  --with-template-objects \
  --with-cgiurl="/cgi-bin/nagios" \
  --with-htmurl="/nagios"

I don't get any errors when running:
/usr/local/nagios-2.0b3/bin/nagios -v
/usr/local/nagios-2.0b3/etc/nagios.cfg


No errors in /var/log/nagios/nagios.log and no errors
in apache.  Any ideas on what I can try?

Thanks.

-Josh

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
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