incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "BORIE (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-1478) Httpd should be restarted just after a fresh installation or an Ambari upgrade
Date Fri, 22 Feb 2013 10:50:12 GMT
BORIE created AMBARI-1478:
-----------------------------

             Summary: Httpd should be restarted just after a fresh installation or an Ambari
upgrade
                 Key: AMBARI-1478
                 URL: https://issues.apache.org/jira/browse/AMBARI-1478
             Project: Ambari
          Issue Type: Bug
          Components: site
    Affects Versions: 1.2.1
         Environment: CentOS 6.3
            Reporter: BORIE


Hello, 

I encountered a problem just after a fresh install of Ambari / or after an ambari-upgrade
from 1.2.0 to 1.2.1, following HortonWorks documentation, on a cluster of hosts. 

The Nagios panel was displaying "No alerts" for each service. Checking in the apache logs,
it was trying to access a page situated at /ambarinagios. This alias is in fact delivered
in /etc/httpd/conf.d/hdp_mon_nagios_addons.conf from package hdp_mon_nagios_addons-1.2.1.2-1.noarch

The logs which result in a 404 error : 

[14/Feb/2013:18:35:46 +0100] "GET /ambarinagios/nagios/nagios_alerts.php?q1=alerts&alert_type=all
HTTP/1.1" 404 323 "-" "Java/1.6.0_31"

An httpd restart/reload just solved my problem because httpd has taken this new conf file
(ie the /ambarinagios alias) into account

Regards, 

Bobo

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message