Long-running Nagios - sudden CGI problems

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Kimmo Jaskari
> Sent: Tuesday, December 07, 2004 7:27 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Long-running Nagios - sudden CGI problems
> 
> This will be lengthy, but I thought I'd better include as much info as
> possible.
> 
> Been running Nagios 1.2 a while now and everything has worked just
fine
> for months. Nagios itself still runs and will no doubt fire off alerts
> if and when a problem occurs. However...
> 
> Suddenly I find that the CGI's refuse to run, giving me the following
> error in the web interface:
> 
> "It appears as though you do not have permission to view information
for
> any of the services you requested...

[snipped]

> I'm stumped. I have no idea where else to look at this point.
> 
> If anyone has any ideas, no matter how farfetched, please chime in.
> Thanks!

This error is also caused by misconfigurations or typographical errors
in your config files. Have you run /path/to/nagios -v
/path/to/nagios.cfg to verify your configuration files. If that returns
no errors, verify that nagios is actually picking up the username
properly. Once you've logged in, nagios will display your username in
the upper right of the main page as 'logged in as ...'. If that shows a
'?' then there is a problem with your htaccess authentication which is
outside of nagios' control.

--
Marc



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.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