FW: Starting up Nagios

[Morris, Patrick]

> Question, couple of questions actually. I am in the process 
> of installing/testing version 2.5, we are currently on 1.2 in 
> production. I have installed it on a Suse linux box, running 
> Suse 9.3, and Apache web server 2.2.3. The initial install 
> seemed to go ok, and I was able to get my configs from 
> production moved over and nagios -v comes up clean. When I 
> try to start nagios it returns an exit 0 (I put a trace in so 
> I could see) but no processes ever start up on the box. I'm 
> also having problems with the add-ons. When trying to run the 
> make all on nrpe I get "no rule to make target 'all'". I get 
> a similar error when trying to do it on nsca "Nothing to be 
> done for 'all'". Could this be part of my problem of it 
> (nagios) not starting up? Any suggestions would be greatly 
> appreciated. Thanks. Also, all of the docs on the web site 
> deal with a new install, are there any docs for an upgrade? 
> Or does anyone have a procedure for upgrading from 1.2 to 
> 2.5? Let me know. Thanks.

Sounds like multiple issues.  On the compilation problems, it sounds
like you don't have a Makefile.  Did you run configure first?  Those
issues are probably unrelated to nagios not starting.

As far as that problem goes, you should be looking in your Nagios log.
If Nagios is not starting, it should say why there, assuming that
however you're starting Nagios actually tries running it.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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