Uploaded image for project: 'Ambari'
  1. Ambari
  2. AMBARI-1478

Httpd should be restarted just after a fresh installation or an Ambari upgrade

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 1.2.1
    • 1.2.2
    • site
    • None
    • CentOS 6.3

    Description

      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

      Attachments

        Activity

          People

            Unassigned Unassigned
            fborie BORIE
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: