Thanks for sharing the output. Yes, that's exactly what I meant (REST API call to get the ATS instances registered with Ambari). To delete the bad ATS instance from Ambari, you can issue the following API call: curl -u admin:admin -k -H "X-Requested-By: ambari" -X DELETE https://localhost:8443/api/v1/clusters/ROGERGPFS/hosts/<hostname-with-bad-ATS>/host_components/APP_TIMELINE_SERVER ... View more

Ambari 2.2.0 did not support HDP 2.4. It was added in Ambari 2.2.1. However, you should use Ambari 2.2.2, as it is more stable. ... View more

It seems like the Grafana daemon is up. Is your Virtualbox set up to port forward 3000? If you do "curl http://localhost:3000" from inside the VM's SSH, what do you see? ... View more

Try: curl -uadmin:admin -H 'X-Requested-By: ambari' -X POST -d '[{"Event": {"specs": [{"principal_type": "users", "sync_type": "existing"}, {"principal_type": "groups", "sync_type": "existing"}]}}]' http://localhost:8080/api/v1/ldap_sync_events You will get a response like: { "resources" : [ { "href" : "http://localhost:8080/api/v1/ldap_sync_events/13", "Event" : { "id" : 13 } } ] } You can GET on this href to get status of the sync: curl -uadmin:admin http://localhost:8080/api/v1/ldap_sync_events/13 { "href" : "http://localhost:8080/api/v1/ldap_sync_events/13", "Event" : { "id" : 13, "specs" : [ { "sync_type" : "existing", "principal_type" : "users" }, { "sync_type" : "existing", "principal_type" : "groups" } ], "status" : "COMPLETE", "status_detail" : "Completed LDAP sync.", "summary" : { "groups" : { "created" : 0, "removed" : 0, "updated" : 0 }, "memberships" : { "created" : 0, "removed" : 0 }, "users" : { "created" : 0, "removed" : 0, "updated" : 0 } }, "sync_time" : { "end" : 1446751142546, "start" : 1446751142462 } } } ... View more