>... query by id filter, ...   For clarification, when you say "=id==" are you referring to "hostId", or the unique "id" of the event. Reason is that in your supplied URL "...query=id==<hostid>", the "id" is a unique ID for an event [1]; however, <hostid> (HOST_IDS) key name within the "attributes" listing [1]. I think your filter is expected to return 0, unless you have valid the "id" for the event.   Does it pull info if you change your query to filter the attributes.HOST_IDS? ie: http://cm:7180/api/v10/events?query=attributes.HOST_IDS==%22<hostid>%22   Let me know if this helps.   [1] https://cloudera.github.io/cm_api/apidocs/v11/ns0_apiEvent.html   ... View more

That seems to be Amazon Linux as you've mentined; are you able to choose RHEL/CentOS AMI, or any of the following listed supported OS [1][2]   [1] http://www.cloudera.com/documentation/enterprise/5-4-x/topics/cm_ig_cm_requirements.html#cmig_topic_4_1_unique_1 [2] http://www.cloudera.com/documentation/director/latest/topics/director_deployment_ami.html ... View more

The first issue has to do with NTP [1] and the second, is when the Agent attempted to read the json contents (possibly Service Monitor metrics), it encoutered an error hece the    Error fetching metrics at 'http://host-hd-01.corp.nodalpoint.com:8086/jmx'   Do you know which for which role the health check is reporting - for a reference, can you attach a screenshot?   [1] http://www.cloudera.com/documentation/enterprise/latest/topics/install_cdh_enable_ntp.html ... View more

  > This indicates that agent is unable to connect to HOSTMONITOR, is HMON running?  [27/Jan/2016 03:16:44 +0000] 3069 MonitorDaemon-Reporter throttling_logger ERROR Error sending messages to firehose: MGMT-HOSTMONITOR-244944378552b77b5c898d702d752f7f   > This indicates that the command timed out when attempting to run a DNS test [1] [27/Jan/2016 03:19:46 +0000] 3069 DnsResolutionMonitor throttling_logger ERROR Timeout with args ['/usr/java/jdk1.7.0_67-cloudera/bin/java', '-classpath', '/usr/share/cmf/lib/agent-5.5.1.jar', 'com.cloudera.cmon.agent.DnsTest']   Example: [bash]# /usr/java/jdk1.7.0_67-cloudera/bin/java -classpath /usr/share/cmf/lib/agent-5.5.1.jar com.cloudera.cmon.agent.DnsTest   > This indicates that supervisord [2] was not running at that time [27/Jan/2016 03:08:52 +0000] 3012 MainThread agent ERROR Failed to connect to previous supervisor.   [1] http://www.cloudera.com/documentation/enterprise/latest/topics/cdh_ig_networknames_configure.html [2] "Agent Process Supervision in Detail" http://blog.cloudera.com/blog/2013/07/how-does-cloudera-manager-work/ ... View more

At first I'd make sure that there's no errors in the the agent log ie: # less /var/log/cloudera-scm-agent/cloudera-scm-agent.log   Also, when you issue the below command is it pointing to the right folder?   # alternatives --display impala-shell     > ... To specify the parcel directory, local parcel repository, add a parcel repository ... that value is only for the .parcel files that CM Server downloads   Please modify your -agent/config.ini uncomment and set the value for the below property, do the same if you have issues on other nodes.   # vi /etc/cloudera-scm-agent/config.ini ... # Parcel directory. Unpacked parcels will be stored in this directory. # Downloaded parcels will be stored in <parcel_dir>/../parcel-cache # parcel_dir=/opt/cloudera/parcels ...   > Can I just symlink to CDH/bin? That is one of Cloudera Agents [1] function - hard restart the agent will normally fix the alternative issues    [1] Agent parse the parcel metadata and creates the alternatives link, see /opt/cloudera/parcels/CDH/meta/alternatives.json     ... View more