Problem starting Nagios 2.0a1

[Thomas W. Capacci]

Dale Hobbs wrote:

> I am having issues starting Nagios 2.0a1. I ran the configure script, 
> make all and make install, and make install-init. The problem that I’m 
> having is that it cannot find the lock file. I thought that the lock 
> file gets created when Nagios starts. Is that not correct? Below is the 
> message that I get when trying to start Nagios.
> 
>  
> 
> Starting network monitor: nagios
> 
> Unable to cd to "/home/nagios"
> 
> No lock file found in /usr/local/nagios/var/nagios.lock
> 
>  
> 
> in /var/log/messages I get this error:
> 
> unable to cd to `/home/nagios' for user `nagios'
> 
>  
> 
> in /usr/local/nagios/var/nagios.log I have this error:
> 
> [1096068327] Nagios 2.0a1 starting... (PID=10011)
> 
> [1096068327] LOG VERSION: 2.0
> 
> [1096068327] You do not have permission to write to 
> /usr/local/nagios/var/nagios.lock
> 
> [1096068327] Bailing out due to errors encountered while attempting to 
> daemonize... (PID=10011)
> 
>  
> 
>  
> 
> I’m not sure what permissions it’s looking for. I have compared the 
> permission for the user ‘Nagios’ with those on a Nagios 1.2 installation 
> and cannot see where the problem lies. Are there different permissions 
> required in 2.0a1?
> 
i've had once this problem i fix it restarting nagios (not stopping or 
starting...-->/etc/init.d/nagios restart or service nagios restart.)


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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