@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

@Tom Burke You can also open the same URL from the Browser where you have logged in the Ambari UI as well. http://ambari.example.com:8443/api/v1/clusters/cluster-name/hosts?fields=Hosts/ip,Hosts/host_name . (OR) You can use the following curl call to produce the JSON output to some file like "/tmp/hosts.json". Also pleas emake sure to use the correct cluster name in the same URL. # curl -k -H "X-Requested-By: ambari" -u admin:admin "http://ambari.example.com:8443/api/v1/clusters/cluster-name/hosts?fields=Hosts/ip,Hosts/host_name" -o "/tmp/hosts.json" . ... View more

@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

@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

@Tom Burke Regarding Ubuntu-18 supportability... you can refer to : Support matrix and click on your version of Ambari to see which all OS it is tested and certified to work with. https://supportmatrix.hortonworks.com/ . Regarding other query "Does the ambari server need to be host member of cluster? ..." No, it is not mandatory to make AmbariServer host to be a member of Cluster. ... View more

@Tom Burke Ideally the "/etc/hosts" file kept identical on all cluster nodes to avoid any kind of hostname confusions. . It is not mandatory to install Agent on the AmbariServer host. (that is optional) . Regarding the "HostNotFoundException" can you please share the output of the following API call to see the hostss (to find out if any conflict) # curl -H "X-Requested-By: ambari" -u admin:admin http://$AMBARI_HOSTNAME:8080/api/v1/clusters/$CLUSTER_NAME/hosts?fields=Hosts/ip,Hosts/host_name . ... View more

@Tom Burke If you define two hostname s inside the "/etc/hosts" file then you might find issues in kerberized environment Example: 192.xx.yy.170 ambari.example.com ambari.corp.example.com . In thew above case we might see that the kerberos clients resolves the incorrect hsotname. So can you please keep only one host there and then try again. Also can you please share the complete message where you see "Host not found, hostname" that way we can check the exact code base to understand in which conditions it might show that message ... View more

@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

@Wael Horchani Please refer to the following Hortonworks HCC article to know how to fix that: https://community.hortonworks.com/articles/61363/issue-oozie-web-console-is-disabledto-enable-oozie.html . Basically you will need to check if "oozie.authentication.cookie.domain" property is added to your "Custom oozie-site" or not? Also please check the following: # wget http://archive.cloudera.com/gplextras/misc/ext-2.2.zip # Stop Oozie service from Ambari # Copy it to the path: "/usr/hdp/current/oozie-client/libext" AND "/usr/hdp/current/oozie-server/libext/" # Regenerate the war file by executing: $ /usr/hdp/current/oozie-server/bin/oozie-setup.sh prepare-war # Start Oozie again . ... View more