Member since
03-14-2016
4721
Posts
1111
Kudos Received
874
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2729 | 04-27-2020 03:48 AM | |
| 5287 | 04-26-2020 06:18 PM | |
| 4456 | 04-26-2020 06:05 PM | |
| 3583 | 04-13-2020 08:53 PM | |
| 5383 | 03-31-2020 02:10 AM |
04-04-2018
11:02 AM
@Krupal Jagtap You can use the Ambari API approach to delete the AMS monitor component. Example: # curl -u admin:admin -H "X-Requested-By: ambari" -X DELETE http://hdfcluster1.example.com:8080/api/v1/clusters/TestCluster/hosts/hdfcluster3.example.com/host_components/METRICS_MONITOR . Here "hdfcluster3.example.com" is the host from where we want to delete the Metrics Monitor. "hdfcluster1.example.com:8080" is ambari server host & port. "TestCluster" is the cluster name. Please replace these values accordingly. Once it is deleted .. it is better to clean the "/etc/ambari-metrics-monitor" directory from that host. And it is also better to take a backup of the mentioned directory and then move it. # mv /etc/ambari-metrics-monitor /etc/ambari-metrics-monitor_BKP
# mv /usr/lib/python2.6/site-packages/resource_monitoring /usr/lib/python2.6/site-packages/resource_monitoring_BKP . Then freshly reinstall the monitor from ambari UI on this host.
... View more
04-04-2018
09:35 AM
@Alexander Schätzle Also please check your KDC configuration to verify if it has default setting something like following or not? # cat /var/kerberos/krb5kdc/kdc.conf
max_life = 24h 0m 0s
max_renewable_life = 7d 0h 0m 0s
default_principal_flags = +renewable, +forwardable .
... View more
04-04-2018
09:23 AM
@Alexander Schätzle As the error says that "TICKET NOT RENEWABLE". Which can happen if the Principal is not having the Renewable attribute. Please check the principal attributes something like this, using "admin.local" utility kadmin: getprinc <PRINCIPAL> Also if you find that it is not having the renewable attributes to it then please modify the principle and add the renewable flags to is something like following:
# modprinc -maxrenewlife "7 days" +allow_renewable krbtgt/XXXX.COM@XXXX.COM
# modprinc -maxrenewlife "7 days" +allow_renewable "amshbase/s0202.cl.xxxx.com@XXXX.COM" . Please use the correct principal names. I have used the masked principal name in the above sample commands. After executing the above commands to modify the principals please run the "kinit -R" to see if its still throwing error while renewing ? .
... View more
04-03-2018
01:47 PM
@Krupal Jagtap The following error might occur if you have installed a slightly different version of Ambari Metrics Monitor compared to the ambari version and hence there are some library mismatch. [WARNING] emitter.py:74 - Error sending metrics to server. 'NoneType' object has no attribute 'strip' 2 . Please check the output of the following command and verify if all the ambari component versions are same? # rpm -qa | grep ambari . Better to freshly try installing the ams monitor. From ambari UI just remove the metrics monitor process and then try installing it again.
... View more
04-03-2018
01:33 PM
@Krupal Jagtap Good to know that now at lease the AMS monitor is coming up. Regarding the "No data available" issue please share the "/var/log/ambari-metrics-monitor/ambari-metrics-monitor.out" Also please check if the "/etc/ambari-metrics-monitor/conf/ambari-metrics-monitor.ini" file is pointing to the Correct Hostname of AMS Collector?
... View more
04-03-2018
12:12 PM
@Krupal Jagtap AMS monitor should come from Ambari repo (not from HDP repo) so please check if you have the amabri.repo file present on that host or not? # cat /etc/yum.repos.d/ambari.repo . If not then please copy and paste that repo file from ambari-server host to this host. Also please make sure that the host where the AMS monitor installation is failing does not have any N/W issue. THis is to ensure that the yum installation for AMS monitor happens without any issue.
... View more
04-03-2018
11:59 AM
@Krupal Jagtap The following error indicates that somehow the yum installation is not happening: Fail(err_msg) resource_management.core.exceptions.Fail: Execution of '/usr/bin/yum -d 0 -e 0 -y install ambari-metrics-monitor' returned 1.
Error: Nothing to do stdout: . So can you please try to do the manual installation of monitor Binaries on that host as following and then continue from Ambari Server UI. # yum clean all
# yum remove ambari-metrics-monitor
# yum install ambari-metrics-monitor . Sometimes incomplete transaction at yum level causes such issue so better to remove the incomplete binary installation first and then try installing it again. Also please check if the "/etc/yum.repos.d/ambari.repo" file on that host is pointing to the correct repo URL and that URL is accessible from the host ? # cat /etc/yum.repos.d/ambari.repo
# cat /etc/yum.repos.d/ambari.repo | grep baseurl .
... View more
04-03-2018
03:02 AM
@Manoj Menon If this answers your query then please mark this HCC thread as answered by clicking on "Accept" link on the correct answer, That way it will help other HCC users to quickly find the answers.
... View more
04-02-2018
12:48 PM
1 Kudo
@Manoj Menon Yarn queue manager tries to get the ambari cluster information using the following API call? http://<AMBARI_FQDN>:8080/api/v1/clusters/<CLUSTER_NAME>; . If you are using "Standalone Ambari View" Server then please check if you are able to make the above API call from the Standalone Ambari View Server? # curl -u admin:admin -H "X-Requested-By: ambari" -X GET http://<AMBARI_FQDN>:8080/api/v1/clusters/<CLUSTER_NAME>; . If you are not using Standalone Ambari View Server then in that case try creating a new instance of the Queue Manager View and then see if it works: Ambari UI --> "Admin" --> "Manage Ambari" --> Views <br> . https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.1.5/bk_ambari-views/content/ch_using_yarn_queue_manager_view.html
... View more
04-02-2018
04:32 AM
@Sergey Sheypak Good idea, Worth to try that.
... View more