Hi

 

Yours configs seems ok!

 

Try „make uninstall“

Your directories and files must be accessed and read by nagios users!

And again read the doc : 
http://nagios.sourceforge.net/docs/3_0/quickstart-fedora.html it’s really 
helpful!

 

 

So, have a nice weekend

jm

 

 

 

Von: Sundar V S [mailto:[email protected]] 
Gesendet: Freitag, 24. April 2009 15:57
An: Meyer Jerome
Cc: Nagios-users
Betreff: Re: [Nagios-users]Nagios Web Interface not Accessible on RHEL 4 AS

 

Hi Meyer,

Thanks for your Response, and for Nagios 3.1 can you tell how to uninstall it, 
as there is no option i am aware of. 

I did gave rites to my nagios location,
chown -R nagios.nagcmd /usr/local/nagios

Also attached with the mail are my httpd.conf and nagios .conf file.

/etc/httpd/conf.d (here nagios.conf) is placed and /etc/httpd/conf (here 
httpd.conf) is placed

Please do provide if any chnages are to be altered in the conf files. Do you 
require any more details on my configuration.

Thanks and Regards,
Sundar

        
        ---------- Original message ----------
        From:Meyer Jerome< [email protected] >
        Date: 24 Apr 09 18:53:21
        Subject: Re: [Nagios-users] Nagios Web Interface not Accessible on RHEL 
4 AS
        To: 

        Could you provide us more infos : like /etc/httpd/conf.d/nagios.conf, 
or /etc/httpd/conf/httpd.conf.

         

        It could be still have some problems!!!!!

         

        First

        ======

        You doesn’t have the right access on your directory or files located 
at /usr/local/nagios/share

         

        Second

        ======

        On RedHat the’s a security enhancement called SELinux and you must 
deactivate it or change it like :

        chcon -R -t httpd_sys_content_t /usr/local/nagios/sbin/

        chcon -R -t httpd_sys_content_t /usr/local/nagios/share

         

        READ CAREFULLY the full guide at 
http://nagios.sourceforge.net/docs/3_0/toc.html 
<http://nagios.sourceforge.net/docs/3_0/toc.html> 

        ===============

         

        THE VERSION 3.1.0 IS ON DEVELOPMENT (TEST), I ENCOURAGE YOU TO USE THE 
STABLE ONE 3.0.6 !!! That’s my point of view…

         

         

        Von: Sundar V S [mailto:[email protected]] 
        Gesendet: Freitag, 24. April 2009 12:52
        An: [email protected]
        Betreff: [Nagios-users] Nagios Web Interface not Accessible on RHEL 4 AS

         

        Hi Friends,

        I am a newbie, installing Nagios 3.1.0 on RHEL 4 AS . I have completed 
the basic installation of Nagios, and now when i am trying to Access the url : 
http://localhost/nagios/ <http://localhost/nagios/>  , and after giving the 
appropriate Username and Password, it is giving following error.

        Forbidden
        You don't have permission to access /nagios/ on this server.
        Apache/2.0.52 (Red Hat) Server at localhost Port 80

        Below given is the extract from the error logs after accessing the Web 
Page, 

        [Thu Apr 23 19:45:39 2009] [error] [client 127.0.0.1] Directory index 
forbidden by rule: /usr/local/nagios/share
        
        [Thu Apr 23 19:45:39 2009] [error] [client 127.0.0.1] File does not 
exist: /var/www/html/favicon.ico

        Please help to resolve this issue, as i am not able to see the Nagios 
Web Interface page.

        Thanks and Regards,
        Sundar

         

        Dear [email protected] ! Get Yourself a cool, short 
@in.com Email ID now! 
<http://mail.in.com/mails/new_reg.php?utm_source=invite&utm_medium=outgoing> 

------------------------------------------------------------------------------
Crystal Reports &#45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty&#45;free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Nagios-users mailing list
[email protected]
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