Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Tue, 30 Apr 2013 18:04:16 +0000 (UTC)
From: "Sumit Mohanty (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12645466.1367343871662.249512.1367345056429@arcas>
In-Reply-To: <JIRA.12645466.1367343871662@arcas>
References: <JIRA.12645466.1367343871662@arcas>
Subject: [jira] [Resolved] (AMBARI-2057) Gmond left in init after install
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMBARI-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sumit Mohanty resolved AMBARI-2057.
-----------------------------------

    Resolution: Fixed
    
> Gmond left in init after install
> --------------------------------
>
>                 Key: AMBARI-2057
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2057
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.3.0
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: 1.3.0
>
>         Attachments: AMBARI-2057.patch
>
>
> Gmond is set to start on boot, so when the server is rebooted our hdp-gmond fails to start. We need to make sure that after we install ganglia we do a : 'chkconfig --del gmond' to make sure the process that does not have our config /etc/init.d/gmond does not start on boot.

--
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