Member since
03-14-2016
4721
Posts
1111
Kudos Received
874
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2463 | 04-27-2020 03:48 AM | |
4914 | 04-26-2020 06:18 PM | |
3987 | 04-26-2020 06:05 PM | |
3241 | 04-13-2020 08:53 PM | |
4951 | 03-31-2020 02:10 AM |
10-17-2018
10:33 PM
1 Kudo
@Lok! Reddy Ambari configurations relies on Hostnames (FQDN= Fully Qualified Hostnames) , As the IPAddress of a host can be variable and might get changed in future due to some system / DNS maintenance. So you will need to make sure that the FQDN of the host is correctly set. You can verify it by running the following command: # hostname -f . If your cluster hosts belongs to some Cloud Platform then the IPAddresses are assigned to ti during the Host creation. You can get the details about your Hosts IPAddress by running the following kind of command: # ifconfig . However if you want to assign a Specific FQDN to your host then you can do it like following: 1. Edit the "/etc/hosts" file and then set the IP Address and Hostname mapping to it Example: # cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
10.10.10.1 newhwx1.example.com
10.10.10.2 newhwx2.example.com
10.10.10.3 newhwx3.example.com
10.10.10.4 newhwx4.example.com
10.10.10.10 my_repo_server.example.com
. In order to setup the FQDN you can do the following: # sysctl kernel.hostname=newhwx1.example.com . Some reference Links: Edit the Host File : https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.0/bk_ambari-installation-ppc/content/edit_the_host_file.html Set the Hostname: https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.0/bk_ambari-installation-ppc/content/set_the_hostname.html Edit the Network Configuration File: https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.0/bk_ambari-installation-ppc/content/edit_the_network_configuration_file.html . Following will be a good read to understand the difference between Public_host_name and Hostname from Ambari perspective. Why ambari host might have different public_host_name and host_name in OpenStack ? : https://community.hortonworks.com/articles/42872/why-ambari-host-might-have-different-public-host-n.html
... View more
10-17-2018
10:32 AM
@Lok! Reddy Also if you see multiple OLD "ambari-hdp-<repoid>.repo" files inside the "/etc/yum.repos.d/" then move the unwanted files from there. Ideally there should be only one file pointing to correct HDP version with accessible baseurl like the file path Example Path # cat /etc/yum.repos.d/ambari-hdp-1.repo .
... View more
10-17-2018
10:22 AM
1 Kudo
@Lok! Reddy On the host where the installation is failing please check if the repos are correct? Specially the baseurl # grep 'baseurl' /etc/yum.repos.d/* | grep HDP
. Also please check if those the link mentioned in the baseurl are accessible? Just append "/repodata/repomd.xml" in the URL and then test if it is accessible? Example: if baseurl is "http://public-repo-1.hortonworks.com/HDP/centos7/2.x/updates/2.6.3.0" then please try accessing it as following to verify the access. Please check all the URLs # curl -v http://public-repo-1.hortonworks.com/HDP/centos7/2.x/updates/2.6.3.0/repodata/repomd.xml . If the URLs are accessible then in that case try cleaning the yum cache by running the command. # yum clean all . After yum clean try running the following command again to verify if the issue persist? # yum -y install ranger_2_6_3_0_235-admin .
... View more
10-17-2018
07:28 AM
1 Kudo
@Lok! Reddy We see the error as following: resource_management.core.exceptions.Fail: Cannot match package for regexp name ranger_${stack_version}-admin. . So it looks like somehow ambari is not able to determine the "${stack_version}" for the ranger admin package. So can you please check if you have something like this in your following two scripts: # grep 'package_version = None' /usr/lib/ambari-server/lib/resource_management/libraries/script/script.py
package_version = None
# grep 'package_version = None' /usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py
package_version = None . On the host where ranger admin installation is failing, can you please try commenting the mentioned line starting with "package_version = None" and then retry from ambari UI to install ranger. # package_version = None .
... View more
10-17-2018
02:23 AM
1 Kudo
@Takefumi Oide From Ambari side currently i do not see any such option to enable the "IPAccessHandler" handler without Ambari Code changes. This is correct that ambari uses Jetty API and it makes use of Handlers "org.eclipse.jetty.server" APIs via Java code (programatic way) but unfortunately it does not use the "IPAccessHandler" directly. https://github.com/apache/ambari/blob/release-2.7.0/ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java#L141-L143 These handlers are added programmatically (not via configuration params) like following code: handlerList.addHandler(gzipHandler); As it is done via Java code hence without code change i do not see an option for ambari to make use of Jetty handler "org.eclipse.jetty.server.handler.IPAccessHandler". It can not be achieved via configuration.
... View more
10-16-2018
07:41 AM
1 Kudo
@Christos Stefanopoulos May be you can try this: 1. Login to Ambari DB (Better take a fresh DB dump of AMbari) 2. Run the following query to see if the View Instalce is associated with the correct Cluster ID (cluster_handle) will be the ID # SELECT view_instance_id,resource_id,view_name, cluster_handle,cluster_type FROM viewinstance . 3. In the above query find the cluster_handle value for working and non working view. If you find a different cluster_handle for your non working view instance then in that case you will need to update it. (For example if all the working view instance has cluster_handle as 4) then you will need to do this. (Suppose your non working view instance ID is 3) # UPDATE viewinstance SET cluster_handle = 4 WHERE view_instance_id=3; .
... View more
10-15-2018
10:10 PM
@Ivan Georgiev Thank you for sharing the parameter.
... View more
10-15-2018
10:08 PM
1 Kudo
@Christos Stefanopoulos By looking at the code which are involved in your stack tarce it looks like Ambari is not able to find the "core-site" config when you are accessing the File View. https://github.com/apache/ambari/blob/trunk/contrib/views/utils/src/main/java/org/apache/ambari/view/utils/hdfs/ConfigurationBuilder.java#L221-L224 This can happen in two scenarios: 1. In a cluster where HDFS services are not installed. >>> However in your case it is not applicable as you mentioned that the HDFS service is installed and running in your cluster. 2. It might happen if the "File View" is somehow not associated with the correct cluster ID. >>> In this case it will be very easy and quick to try this " Create a new File View Instance" and then test it. Ambari UI --> "admin" (drop down) --> Manage Ambari --> Views --> Create Instance --> Select "File" View and just create a new Instance of File view and then test it.
... View more
10-11-2018
10:35 AM
@Amit Mishra What is your HDP version? Ambari 2.7 Supports HDP 3.0 So please make sure that your HDP components are upgraded fine. To know more about supportmatrix: https://supportmatrix.hortonworks.com/ . https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.0.0/bk_ambari-upgrade/content/ambari_upgrade_guide.html Ambari 2.7only supports fully managing a HDP 3.0cluster. If you are running any other HDP version,you must first upgrade to HDP 2.6 using Ambari 2.6. You must first upgrade to HDP 2.6.5 if you use Hive.Then, upgrade to Ambari 2.7 and use it to upgrade your cluster to HDP 3.0.
... View more