@sysconfdir@/cgi.cfg - Installation setup problem

[Subhendu Ghosh]

On Wed, 31 Aug 2005, Elizar M. Palad wrote:

> Hi list!
> This is my first time in nagios and first time in this list.
> I tried following the direction in the documentation in the source
> and browsed the archive for this basic/common (iguess) problem
> in setting up nagios. I hope someone out there can help me.
> When i access nagios using IE (http://localhosts/nagios) the
> web interface shows up, but clicking the monitoring links (cgis)
> i have this:
> Whoops!
>
> *Error: Could not open CGI config file '@sysconfdir@/cgi.cfg' for reading!*
> I have every config file in /usr/local/nagios/etc
> (cgi.cfg, nagios.cfg and other cfg files)
> pre-flight check shows no errors
>
> Total Warnings: 0
> Total Errors: 0
>
> Things look okay - No serious problems were detected during the pre-flight
> check
>
> What could be wrong? what did i miss? no errors in apache logs or in
> configuation of httpd.conf.
> Help me please? someone? if there's additional info you guys might need,
> please let me know..
> thanks!
> eli
>
>

Did you do your own compile or install from somewhere else?

1. Pre-flight check does not looks at cgi.cfg (not needed for nagios to 
function - only the UI)
2. @sysconfdir@ is supposed to be replaced at "configure" time before 
compile. The base path is hardcoded into the cgis.

Looks like either the compile process bombed or you have a bad package.

-- 
-sg


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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