Wierd problem

[Leonardo Henrique Machado]

Check the permissions of your .cfg files. If one of them are owned by
root, nagios does not start but dies silently.

cfg files must be readable by nagios user.


On Tue, 14 Dec 2004 10:29:27 -0500, Daniel Corbe
<daniel.junkmail at gmail.com> wrote:
> Hi,
> 
> I'm running nagios 1.2 and I'm getting a wierd problem.  I've started
> nagios and it seems like everything works because I don't get any
> error messages and nagios -v doesn't complain about my config files;
> however when I go to pull up the Nagios service overview (or anything
> other than the nagios start page) I get the Whoops! page instead.
> 
> Nagios has been successfully authenticating to my postgresql server
> and has access to the data  but does not appear to be updating the
> database and there are no errors in the error log.
> 
> -------------------------------------------------------
> 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
> 


-- 
Leonardo Henrique Machado


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