Awesome. The referred Articles helped me solve my ambari-metrics restart issue. Here is the short form of the steps 1) Stop Ambari Metrics Collector and Grafana 2) Backup the embedded hbase and hbase-temp folders and deleted them. (The paths could differ from default. So I looked up the hbase.rootdir and hbase.tmp.dir properties in Ambari > Ambari Metrics > Config for the appropriate path) 3) Restart Ambari Metrics Collector and Grafana The Ambari Metrics Collector Started correctly without any errors. Note: As you may have suspected, by deleting the existing hbase folder, you will loose the metrics history. ... View more

@Kyle Pifer, I know you found a workaround now; nevertheless, we found the solution (because we experienced the same issue, the hard way): tez view is the problem. If you look at your ambari-server.log, you can see it tries to deploy the tez view, but never confirms it did. I don't know what's wrong with the tez view, neither why it only prevents starting ambari now since we did thousands of server restart for the past year, but if you move the tez view jar in /var/lib/ambari-server/resources/views to another folder, then ambari will start properly. Now, if you need the tez view, debugging it is another story... Hope this helps, cheers. ... View more

Agent log is under /var/log/ambari-agent/ambari-agent.log but it sounds like you are still trying to install agents via Ambari UI. To install them manually use the instructions in the above doc (e.g. apt-get install ambari-agent) Then as the doc states, this is the property to set to point the agent to the ambari-server node $ cat /etc/ambari-agent/conf/ambari-agent.ini | grep hostname hostname=sandbox.hortonworks.com Once the property is set, you can restart the agent ... View more