Support Questions

Find answers, ask questions, and share your expertise

Ambari metircs not started

avatar
Contributor
/Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_collector.py", line 90, in <module>
    AmsCollector().execute()
  File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 355, in execute
    self.execute_prefix_function(self.command_name, 'post', env)
  File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 382, in execute_prefix_function
    method(env)
  File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 424, in post_start
    raise Fail("Pid file {0} doesn't exist after starting of the component.".format(pid_file))
resource_management.core.exceptions.Fail: Pid file /var/run/ambari-metrics-collector//hbase-ams-master.pid doesn't exist after starting of the component./
1 ACCEPTED SOLUTION

avatar
Expert Contributor

Hi@Manoj690 ,

 

Seems your AMS hbase master is not able to start -

 

 

Please try below steps -

 

  1. In the Ambari Dashboard, go to the 'Ambari Metrics' section and under the 'Service Actions' dropdown click 'Stop'. 
  1. Check and confirm from backend that ams process is stopped. If the process is still running use below command to stop -
    # ambari-metrics-collector stop
  1. Delete all AMS Hbase data -
    1. In the Ambari Dashboard, under the Ambari Metrics section do a search for the following configuration values  "hbase.rootdir"
    1. Remove entire files from “hbase.rootdir”
      Eg.  #hdfs dfs -cp  /user/ams/hbase/* /tmp/
              #hdfs dfs -rm -r -skipTrash  /user/ams/hbase/*
    2. In the Ambari Dashboard, under the Ambari Metrics section do a search for the following configuration values  “hbase.tmp.dir”. Backup the directory and remove the data.

Eg. #cp /var/lib/ambari-metrics-collector/hbase-tmp/*  /tmp/

       #rm –fr /var/lib/ambari-metrics-collector/hbase-tmp/*

  1. Remove the znode for hbase in zookeeper cli
    Login to ambari UI -> Ambari Metrics -> Configs -> Advance ams-hbase-site and search for property  “zookeeper.znode.parent”

#/usr/hdp/current/zookeeper-client/bin/zkCli.sh

#rmr /ams-hbase-secure  

  1. Start AMS

 

Let know if you still have issue

 

View solution in original post

1 REPLY 1

avatar
Expert Contributor

Hi@Manoj690 ,

 

Seems your AMS hbase master is not able to start -

 

 

Please try below steps -

 

  1. In the Ambari Dashboard, go to the 'Ambari Metrics' section and under the 'Service Actions' dropdown click 'Stop'. 
  1. Check and confirm from backend that ams process is stopped. If the process is still running use below command to stop -
    # ambari-metrics-collector stop
  1. Delete all AMS Hbase data -
    1. In the Ambari Dashboard, under the Ambari Metrics section do a search for the following configuration values  "hbase.rootdir"
    1. Remove entire files from “hbase.rootdir”
      Eg.  #hdfs dfs -cp  /user/ams/hbase/* /tmp/
              #hdfs dfs -rm -r -skipTrash  /user/ams/hbase/*
    2. In the Ambari Dashboard, under the Ambari Metrics section do a search for the following configuration values  “hbase.tmp.dir”. Backup the directory and remove the data.

Eg. #cp /var/lib/ambari-metrics-collector/hbase-tmp/*  /tmp/

       #rm –fr /var/lib/ambari-metrics-collector/hbase-tmp/*

  1. Remove the znode for hbase in zookeeper cli
    Login to ambari UI -> Ambari Metrics -> Configs -> Advance ams-hbase-site and search for property  “zookeeper.znode.parent”

#/usr/hdp/current/zookeeper-client/bin/zkCli.sh

#rmr /ams-hbase-secure  

  1. Start AMS

 

Let know if you still have issue