Ambari built. Network on virtual machines set. Trying to install cluster with the installation wizard of ambari UI. Could not get passed from "Get Started" to "Select version".
There is this error in the logs:
Could not load repo results
java.io.IOException: Server returned HTTP response code: 403 for URL: http://s3.amazonaws.com/dev.hortonworks.com/HDP/hdp_urlinfo.json
Found question with same problem which was not resolved
Screenshot from UI:
#eGs
It looks like you missed some steps and prerequisites before installing ambari. 127.0.0.1 should not be used to access the UI. Ambari docs require use to use FQDNs for all nodes and hosts.
Additionally, the 403 error above is result from using versions of ambari/hdp which cloudera has moved behind a paywall. User/password is required to access these assets now.
You should try with Ambari 2.7.4 and repos and artifacts that are not behind a paywall.
Related
I'm trying to get my own cluster with Ambari following this official guide https://cwiki.apache.org/confluence/display/AMBARI/Quick+Start+Guide#space-menu-link-content. But I cannot copy repository on this command wget -O /etc/yum.repos.d/ambari.repo http://public-repo-1.hortonworks.com/ambari/centos7/2.x/updates/2.5.1.0/ambari.repo
I am using centos7.4
As a result I have problem 403:Forbidden. I also tried to get this page via browser but I got an error.
I also tried to use one of this repos https://docs.cloudera.com/HDPDocuments/Ambari-2.2.0.0/bk_Installing_HDP_AMB/content/_ambari_repositories.html or similar but there's still nothing.
Could you help me guys?)
"Effective Jan 31, 2021, all Cloudera software requires a subscription and must be accessed via the paywall", please check https://www.cloudera.com/downloads.html
I was using Ambari Server UI to register a node as an agent and the registration kept failing. I checked the ambari-agent logs at /var/log/ambari-agent/ and found the following line in the logs
Registration failed due to: Cannot register host with not supported os type, hostname=scope, serverOsType=ubuntu19, agentOsType=ubuntu19
I understand this is because I have Ubuntu 19.04. Is this any workaround for this?
I confirm the answer, it is an ambari version problem so apply this solution to you it works
If you want to give it a try, the list of os and their versions supported by ambari can be found under this path ( on Ambari server host and on Ambari agent hosts )
/var/lib/ambari-agent/tmp/ambari_commons/resources/os_family.json
or
/usr/lib/ambari-server/lib/ambari_commons/resources/os_family.json
You can add the ambari version you are using and restart ambari
This is probably because the ambari version you are using doesn't support this version of ubuntu: this means in reality that ambari is not yet officially tested against that version.
If you want to give it a try, the list of os and their versions supported by ambari can be found under this path ( on Ambari server host and on Ambari agent hosts )
/var/lib/ambari-agent/tmp/ambari_commons/resources/os_family.json
or
/usr/lib/ambari-server/lib/ambari_commons/resources/os_family.json
You can add the ambari version you are using and restart ambari
I have installed cm6 already, and want to install cloudera manager agent from custom repository and CDH6 with using packages.
(I work with only one host)
I have files for cloudera manager agent in directory /cloudera/cloudera-repo/cm6/6.0.1 and for CDH6 in directory /cloudera/cloudera-repo/cdh6/6.0.1
My steps for Cloudera Manager Agent:
Custom repository -> choose http://ip_addr/cloudera/cloudera-repo/cm6/6.0.1
For CDH and other software:
Install Method -> Use Packages
CDH Version -> CDH6
CDH Minor Version -> choose http://ip_addr/cloudera/cloudera-repo/cdh6/6.0.1
And on page Install Agents I have such error:
Failed to copy installation files
/tmp/scm_prepare_node.xpsM8dvM
Connection refused (Connection refused)
I have same error even when I specify empty directories. Why?
From the error, it seems that you have not provided proper credentials to connect to your host. The ssh credentials seems to be incorrect. If you are sure, ssh credentials are fine, then it is a firewall issue. You need to make sure all the required ports are enabled and no blocker is there for cloudera to install the agent.
I have downloaded the latest HDP 2.6.5 from Hortonworks website. Following the instructions in the section 'MAP SANDBOX IP TO YOUR DESIRED HOSTNAME IN THE HOSTS FILE
' from the link -
https://hortonworks.com/tutorial/learning-the-ropes-of-the-hortonworks-sandbox/#determine-ip-address-of-your-sandbox
I added the details to the hosts file. When I try the site sandbox.hortonworks.com or any of the ones mentioned in the mapping, I get the error 'Site can't be reached'.
I am using Macbook and running the Sandbox on VirtualBox. I am able to log on to the command line using the url http://localhost:4200 and Ambari via http://localhost:8080/#/login.
I just want to know why I am not able to get it working using sandbox.hortonworks.com
Just add the port after your link:
sandbox.hortonworks.com:4200
or
sandbox.hortonworks.com:8080
i have done an hadoop cluster installation with cloudera manager. After this installation impala status has become bad.
I have the following error for master node:
Web Server Status
and this one for nodes with imapala daemon:
Impala Daemon Ready Check, Web Server Status
looking into logs i have found some errors:
The health test result for IMPALAD_WEB_METRIC_COLLECTION has become bad: The Cloudera Manager Agent got an unexpected response from this role's web server.
looking into cloudera-scm-agent.log there are those errors:
1261 Monitor-HostMonitor throttling_logger ERROR (29 skipped) Failed to collect NTP metrics
i tryed to install NTP (sudo apt-get install ntp) but after this installation HDFS, HIVE, YARN and others services goes bad, removing that only impala goes bad.
MainThread agent ERROR Failed to connect to previous supervisor.
Another error is this:
Monitor-GenericMonitor throttling_logger ERROR Error fetching metrics at 'http://nodo-1:50075/jmx'
i tried looking all hostnames and seems correct...
so, what is this problem? how can i solve it?
I also had problem with NTP, the problem still existed after installing NTP , but when I done sudo service ntp restart the error was fixed