Member since
03-14-2016
4721
Posts
1111
Kudos Received
874
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2825 | 04-27-2020 03:48 AM | |
| 5479 | 04-26-2020 06:18 PM | |
| 4661 | 04-26-2020 06:05 PM | |
| 3702 | 04-13-2020 08:53 PM | |
| 5604 | 03-31-2020 02:10 AM |
02-06-2019
12:50 AM
@Tom Burke And regarding the SSL related issue. You will need to make sure that you configure a truststore in ambari Server and import the LDAP/AD certificate to Ambari Server's truststore to fix the following message: Failed to connect to KDC - Failed to communicate with the Active Directory at ldaps://xxx.yyy.com:636: simple bind failed: xxx.yyy.com:636 . Please see: https://community.hortonworks.com/content/supportkb/148572/failed-to-connect-to-kdc-make-sure-the-servers-ssl.html
... View more
02-06-2019
12:46 AM
@Tom Burke Looks like the FQDN is not set correctly on your failing Node. Please run the following commands to verify if the FQDN is setup correctly? (hostname and FQDN are not same) # python<<<"import socket;print socket.getfqdn();"
(OR)
# hostname -f
# hostname
If you find a difference in the FQDN then please set the FQDN of your host correctly. You can find the details here about hostname and public_hostname: https://community.hortonworks.com/content/kbentry/42872/why-ambari-host-might-have-different-public-host-n.html
... View more
02-06-2019
12:40 AM
@Tom Burke I think everything is fine and i see no errors any more in the UI operational logs or in the ambari-agent logs. So it looks good to me. Do you still see any issue?
... View more
02-06-2019
12:18 AM
@Tom Burke Looks like ambari agent is already installed on your ambari server host. So just try to start it and then see it it is starting fine without any error. # ambari-agent start; tail -f /var/log/ambari-agent/ambari-agent.log .
... View more
02-06-2019
12:06 AM
@Tom Burke i meant to say on the host where the Agent registration is failing can you check from where Ambari 2.2.1.0 binaries are coming because we saw in your output as : http://public-repo-1.hortonworks.com/ambari/ubuntu14/2.x/updates/2.2.1.0 Ambari . Or can you please share the "ambari-agent.log" from the host where the agent setup is failing? "/var/log/ambari-agent/ambari-agent.log"
... View more
02-05-2019
11:57 PM
@Tom Burke Can you also please check on the agent host to know why it is referring to Old ambari version 2.2.1.0? May be on the problematic host you can try running this command to find out which version is it using?
# dpkg --list | grep ambari .
... View more
02-05-2019
11:18 PM
@Tom Burke This time i do not see it is failing with the the previous error. But it is strange to see that you are planning to use too old Ambari 2.2.1.0 as i see your output as following: Get:1 http://public-repo-1.hortonworks.com/ambari/ubuntu14/2.x/updates/2.2.1.0 Ambari InRelease [3,187 B] . Is there any specific reason for choosing so old Ambari version? Latest ambari release is 2.7.3 .
... View more
02-05-2019
10:34 PM
@Tom Burke 1. Please make sure that the permission on these files are correct as following: # ls -lart /root/.ssh/
total 20
-rw-r--r--. 1 root root 409 Jul 21 2018 id_rsa.pub
-rw-------. 1 root root 1679 Jul 21 2018 id_rsa . 2. Also please make sure that the id_rsa files are generated on the host after fixing the hostname. (if the host was having multiple hostname earlier then please regenerate the keys again) Also make sure to copy this public key to the mentioned hosts (and all cluster hosts) # ssh-copy-id -i ~/.ssh/id_rsa.pub root@ambari.example.com . 3. Also for a quick check if the passwordless SSH is setup already then you should be able to do SSH without entering password nexttime. # ssh root@ambari.example.com
... View more
02-03-2019
10:19 PM
1 Kudo
@Wael Horchani There seems to be some issue with the "hdp-select" command as well. Like i see an error when you are running the simple "hdp-select" command. . Also in your case the Oozie version might be slightly different (due to a slight different HDP version) so please check which repo is providing you oozie packages which are installed to your host: # yum info oozie* . Also please make sure that the host where you are checking the Oozie is correct host. I means please verify by logging in to the Oozie server host using SSH using IP Address instead of using Hostname for SSH (as sometimes it might be possible that we use incorrect IP-Host mapping inside "/etc/hosts" entry on our local machine so that while doing SSH wee go to a different host) .
... View more
02-03-2019
10:53 AM
@Wael Horchani Ideally the path should exist in HDP 2.6.5 as well. Example: [root@newhwx3 ~]# ls -ld /usr/hdp/current/oozie-client/libext
drwxr-xr-x. 2 root root 6 May 11 2018 /usr/hdp/current/oozie-client/libext
[root@newhwx3 ~]# ls -ld /usr/hdp/current/oozie-server/libext/
drwxr-xr-x. 2 root root 6 May 11 2018 /usr/hdp/current/oozie-server/libext/
[root@newhwx3 ~]# hdp-select | grep oozie
oozie-client - 2.6.5.0-292
oozie-server - 2.6.5.0-292 . Can you please check if you have the Oozie package installed properly? # yum info oozie_2_6_5_0_292* If not installed properly then you can try reinstalling it as following # yum reinstall oozie_2_6_5_0_292* . Path to Oozie WAR: [root@newhwx3 ~]# locate oozie.war
/usr/hdp/2.6.5.0-292/oozie/oozie.war
/usr/hdp/2.6.5.0-292/oozie/webapps/oozie.war
[root@newhwx3 ~]# ls -l /usr/hdp/2.6.5.0-292/oozie/webapps/oozie.war
-rw-r--r--. 1 root root 0 May 11 2018 /usr/hdp/2.6.5.0-292/oozie/webapps/oozie.war
.
... View more