Long-running Nagios - sudden CGI problems

[Andreas Ericsson]

Kimmo Jaskari wrote:
> On Tue, 2004-12-07 at 07:54 -0600, Marc Powell wrote:
> 
>>>-----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.
> 
> 
> I did make a very minor alteration in the config file where I keep the
> info for the Solaris machines... and I mean very minor, changed a
> description for one machine. I find it difficult to believe I managed to
> foul that up somehow but will of course re-check.
> 

You need to restart nagios as well, or the logs will have entries for 
hosts and services the cgi's can't find.

> I did, of course, do the -v run before posting to the mailgroup to make
> sure Nagios wasn't choking on the config files and that went well, but I
> guess I'd better take a more thorough look at that config file just to
> make sure.
> 
> I do see "logged in as kimmoj" in Nagios, and Nagios does demand that I
> log in and use a name/password combo that's valid.
> 
> Thanks, I'll re-check the config file and see if I can find the problem.
>

Be sure to check the permissions then as well. If the cgi's can't read 
one of the object config files it should throw an(other) error, but it 
was some time since I dabbled with 1.x so I might remember this wrong.


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

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


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