[
https://issues.apache.org/jira/browse/AMBARI-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586166#comment-13586166
]
Jeff Markham commented on AMBARI-1492:
--------------------------------------
For the attached files, here's what needs to be done:
1. On the Ganglia server node, make sure Apache is started, the native Ganglia
server is stopped, and the HDP-controlled Ganglia is started:
{code}
> chkconfig httpd on
> sed -i ‘3i# chkconfig: 2345 80 80’ /etc/init.d/hdp-gmetad
> chkconfig hdp-gmetad on
> chkconfig gmetad off
{code}
2. On all the Ganglia agent nodes, make sure the Ganglia agents start with
chkconfig:
{code}
> sed -i ‘3i# chkconfig: 2345 80 80’ /etc/init.d/hdp-gmond
> chkconfig hdp-gmond on
{code}
3. On the Nagios server node, make sure Apache is started and that the Nagios
collector is on:
{code}
> chkconfig httpd on
> chkconfig nagios on
{code}
4. On the Nagios agent nodes, make sure SNMP is started:
{code}
> chkconfig snmpd on
{code}
5. Copy ambari-server file to the Ambari server node into /etc/init.d/ and
turn chkconfig on:
{code}
> chkconfig ambari-server on
{code}
6. Copy ambari-agent file to the Ambari agent node into /etc/init.d/ and turn
chkconfig on:
{code}
> chkconfig ambari-agent on
{code}
After doing these steps, you should have an Ambari-controlled cluster that can
restart with all metrics and graphs appearing normally.
> Add init.d scripts for Ambari server + agent
> --------------------------------------------
>
> Key: AMBARI-1492
> URL: https://issues.apache.org/jira/browse/AMBARI-1492
> Project: Ambari
> Issue Type: Bug
> Reporter: Jeff Sposetti
> Attachments: ambari-agent, ambari-server
>
>
> Add init.d scripts for Ambari server + agent to control start/stop/status.
> Also include support for chkconfig
--
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
