Member since
03-14-2016
4721
Posts
1111
Kudos Received
874
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2712 | 04-27-2020 03:48 AM | |
| 5271 | 04-26-2020 06:18 PM | |
| 4440 | 04-26-2020 06:05 PM | |
| 3565 | 04-13-2020 08:53 PM | |
| 5367 | 03-31-2020 02:10 AM |
05-05-2017
07:47 AM
1 Kudo
@frank chen From your logs we see that agents are failing to communicate with ambari-server. INFO 2017-05-05 14:05:11,156 NetUtil.py:67 - Connecting to https://centos7-node1:8440/ca
WARNING 2017-05-05 14:05:11,157 NetUtil.py:98 - Failed to connect to https://centos7-node1:8440/ca due to [Errno 111] \xe6\x8b\x92\xe7\xbb\x9d\xe8\xbf\x9e\xe6\x8e\xa5
WARNING 2017-05-05 14:05:11,157 NetUtil.py:121 - Server at https://centos7-node1:8440 is not reachable, sleeping for 10 seconds...
Please make sure that the agents are able to access the ambari-server hostname & port properly. There should be no iptables/firewall restriction.
Please check that you are able to do telnet from agent machine to connect to ambari server? 8440: Handshake Port for Ambari Agents to Ambari Server 8441: Registration and Heartbeat Port for Ambari Agents to Ambari Server # telnet centos7-node1 8440
# telnet centos7-node1 8441
# telnet centos7-node1 8080 Also on ambari server and agent hosts please make sure that the hostnames are resolvable throughout the cluster (means every host has the correct "/etc/hosts" entry to resolve other hosts. The output of the following command shoudl be resolvable and consistent through out the cluster hosts. # hostname -f https://docs.hortonworks.com/HDPDocuments/Ambari-2.4.2.0/bk_ambari-installation/content/set_the_hostname.html .
... View more
05-04-2017
01:01 PM
@Ward Bekker In the Ambari UI --> HDFS --> Configs --> Advanced --> "hadoop-env template" you will see the "SHARED_HADOOP_NAMENODE_OPTS" variable that is setting the -Dhdfs.audit.logger=INFO,DRFAAUDIT
Above actually controls the audit logging. So you might want to delete that "hdfs.audit.logger" system property from the if-else block (same for HADOOP_DATANODE_OPTS option as well) {% if java_version < 8 %}
SHARED_HADOOP_NAMENODE_OPTS= ........
{% else %}
SHARED_HADOOP_NAMENODE_OPTS=
{% endif %} . After that when we restart the HDFS components then in the "ps -ef | grep NameNode" we should not see the "-Dhdfs.audit.logger=INFO,DRFAAUDIT" .
... View more
05-04-2017
09:20 AM
1 Kudo
@Akash S Making changes to "dfs.datanode.failed.volumes.tolerate=1" will not ask for HBase restart. After making this change you might see a restart required services as "HDFS", "MapReduce2" and "YARN".
... View more
05-03-2017
09:38 AM
1 Kudo
@ARUN
The following HDP2.6 document talks about incremental backups of HBase.
https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.0/bk_data-access/content/ch_hbase_bar.html
... View more
05-02-2017
09:13 AM
1 Kudo
@Sandeep Rai
You will need to write the hostname mapping file to define the Hostname (FQDN) mapping with the hostgroups, Blueprint File does not contain the actual Hostnames, Instead it uses
the placeholders for the hosts like 'host_group_2', 'host_group_3'
.etc.You will need to provide another JSON file to specify the hostgroup mapping. For more practice example please refer to: https://github.com/abajwa-hw/ambari-workshops/blob/master/blueprints/cluster-4node.jsonAnd https://cwiki.apache.org/confluence/display/AMBARI/Blueprints#Blueprints-ExampleClusterCreationTemplate.1 .
... View more
04-30-2017
08:07 AM
1 Kudo
@Michael Londeen Are you using ActiveDirectory or LDAP in your setup? Can you please try setting the "ignore_groupsusers_create" parameter value to "true" and then ry restarting the services again? Example:
# /var/lib/ambari-server/resources/scripts/configs.sh set <AMBARI_FQDN> <CLUSTER_NAME> cluster-env "ignore_groupsusers_create" "true"
It will made it skip users and groups creating part. Basically enabling this flag, user have to create users/groups on his own, So Ambari will not attempt to create the hadoop group for you and expected the group exists. .
... View more
04-27-2017
11:21 AM
@Edgar Daeds Caused by: java.security.GeneralSecurityException: Checksum failed
at sun.security.krb5.internal.crypto.dk.AesDkCrypto.decryptCTS(AesDkCrypto.java:451) Usually the above kind of error occurs when: 1. Either the password that you entered is wrong. So verify if the "kinit" is working fine from that host?
2. The keytab might be containing an older version of the keytab credentials in it and hence it cannot parse the information coming from the KDC, as it lacks the up to date credentials.
3. Kerberos is strict about hostnames so please check if you are using correct Hostnames/FQDN?
4. Are you using correct JDM (like JDP 😎 along with the "JCE extension package" ? 5. Can you please do a klist using "-kte" flags, Specially "e" to verify if it is using correct encryption klist -kte /etc/security/keytabs/hbase.service.keytab
.
... View more
04-20-2017
05:10 PM
@Baruch AMOUSSOU DJANGBAN Please check if by any chance you have the "/etc/zeppelin/conf/interpreter.json" if it has correct read permission and also if the data inside this file is correct Or got corrupted by any chance. - Also it will be good to try moving the "/usr/hdp/2.5.0.2-3/zeppelin/webapps/" directory to some other directory and then restart Zeppelin. Example: # mv /usr/hdp/2.5.0.2-3/zeppelin/webapps /Backup .
... View more
04-19-2017
11:10 AM
1 Kudo
@Paul ski You should check few things:
1). SSH to the Sandbox as following and check whether ambari-server is running fine or not and if it is listening to the correct port or not ? # ssh root@localhost -p 2222
# ambari-server status
# netstat -tnlpa | grep `cat /var/run/ambari-server/ambari-server.pid`
2). If the ambari server is running and listening to the correct port 8080 then try logging into ambari using default credentials:
http://localhost:8080/
username: maria_dev
password maria_dev
3). If you still face any issue or would like to change the ambari admin credential then run the following command "/usr/sbin/ambari-admin-password-reset": # ambari-admin-password-reset
Please set the password for admin:
4). If it still does not work then please check of your VirtualBox has the Network Port Forwarding enabled or not for port 8080? .
... View more
04-19-2017
09:19 AM
@Allen Niu Similarly you can try the same form TEZ_CLIENT as well. curl -iv -u admin:admin -H "X-Requested-By: ambari" -X DELETE http://<AMBARI_HOST>:8080/api/v1/clusters/<CLUSTER_NAME>/hosts/<HOST.NAME>/host_components/TEZ_CLIENT . Once those are gone from the UI then you can freshly try to reinstall those clients from ambari ui.
... View more