On Jan 19, 2009, at 8:34 PM, Khairuzzamri wrote:

> Installation run smoothly, but I cannot add the nagios to the  
> startup routine:
>  [r...@localhost]# chkconfig –add nagios
>  [r...@localhost]# chkconfig nagios on
>
> Both give 'error reading information on service nagios: No such file  
> or directory'.

Sounds like you didn't install the init script.

Step 3 of http://nagios.sourceforge.net/docs/3_0/quickstart- 
fedora.html --

make install-init

> But when I verify the nagios configuration files:
> [r...@localhost]# /usr/local/nagios/bin/nagios -v /usr/local/nagios/ 
> etc/nagios.cfg
>
> It stated 'No warning & no errors'.

This just checks your nagios configuration (nagios.cfg and any  
cfg_files or resource_files referenced within it) for obvious syntax  
errors. It doesn't check apache configuration, startup scripts,  
whether your plugins exist/work, etc, etc.

> 1 more thing if I'm go to the nagios page, even I'm providing the  
> correct username and password, it wont let me in.

That would be an apache configuration problem. Check your apache error  
logs for information. If there's nothing interesting there, expand on  
what you mean by 'wont let me in' and the exact configuration steps  
you've taken so far. You might want to also read/review the actual  
nagios quick start guide above to make sure the one you're reading  
didn't miss steps.

> Am I missing something here, or is Nagios 3.0.3 is not compatible  
> with Redhat 9?

There are no incompatibilities with any flavor of linux that I am  
aware of. Nagios has pretty minimal requirements.

--
Marc


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Nagios-users mailing list
Nagios-users@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

Reply via email to