incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Sposetti (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-2057) Gmond left in init after install
Date Mon, 20 May 2013 01:04:13 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661700#comment-13661700
] 

Jeff Sposetti commented on AMBARI-2057:
---------------------------------------

FWIW: Possibly found by users in the community

http://.hortonworks.com/community/forums/topic/lack-of-cluster-metrics-following-fresh-hdp-install-on-4-nodes/
                
> 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.2.3
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: 1.2.4
>
>         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

Mime
View raw message