ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitaly Brodetskyi (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-5031) gmetad/gmond left in init after install
Date Tue, 11 Mar 2014 18:03:43 GMT

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

Vitaly Brodetskyi resolved AMBARI-5031.
---------------------------------------

    Resolution: Fixed

Committed to trunk

> gmetad/gmond left in init after install
> ---------------------------------------
>
>                 Key: AMBARI-5031
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5031
>             Project: Ambari
>          Issue Type: Bug
>          Components: agent
>    Affects Versions: 1.5.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 1.5.0
>
>         Attachments: AMBARI-5031.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 was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message