Try the recommended solution for each of the following problems:
Your browser crashes or you accidentally close your browser before the Install Wizard completes.
The response to a browser closure depends on where you are in the process:
The browser closes before you press the
Deploy
button.Re-launch the same browser and continue the install process. Using a different browser forces you to re-start the entire process.
The browser closes after you press
Deploy
, while or after theInstall, Start, and Test
screen opens.Re-launch the same browser and continue the process, or log in again, using a different browser. When the
Install, Start, and Test
displays, proceed.
The Install, Start, and Test screen reports that the cluster install has failed.
The response to a report of install failure depends on the cause of the failure:
The failure is due to intermittent network connection errors during software package installs.
Use the
Retry
button on theInstall, Start, and Test
screen.The failure is due to misconfiguration or other setup errors.
Use the left navigation bar to go back to the appropriate screen. For example,
Customize Services
.Make your changes.
Continue in the normal way.
The failure occurs during the start/test sequence.
Click
Next
andComplete,
then proceed to theMonitoring Dashboard
.Use the
Services View
to make your changes.Re-start the service using
Service Actions
.
The failure is due to something else.
Open an SSH connection to the Ambari Server host.
Clear the database. At the command line, type:
ambari-server reset
Clear your browser cache.
Re-run the Install Wizard.
When deploying HDP using Ambari 1.4.x or later on RHEL CentOS 6.5, click the “Failed” link on the Confirm Hosts page in the Cluster Install wizard to display the Agent logs. The following log entry indicates the SSL connection between the Agent and Server failed during registration:
INFO 2014-04-02 04:25:22,669 NetUtil.py:55 - Failed to connect to https://{ambari-server}:8440/cert/ca due to [Errno 1] _ssl.c:492: error:100AE081:elliptic curve routines:EC_GROUP_new_by_curve_name:unknown group
For more detailed information about this OpenSSL issue, see https://bugzilla.redhat.com/show_bug.cgi?id=1025598
In certain recent Linux distributions, such as RHEL/Centos/Oracle Linux 6.x, the
default value of nproc
is lower than the value required to deploy the
HBase service successfully. If you are deploying HBase, change the value of
nproc
:
Check the OpenSSL library version installed on your host(s):
rpm -qa | grepopenssl openssl-1.0.1e-15.el6.x86_64
If the output reads
openssl-1.0.1e-15.x86_64 (1.0.1 build 15),
you must upgrade the OpenSSL library. To upgrade the OpenSSL library, run the following command:yum upgrade openssl
Verify you have the newer version of OpenSSL (1.0.1 build 16):
rpm -qa | grep opensslopenssl-1.0.1e-16.el6.x86_64
Restart Ambari Agent(s) and click
Retry -> Failed
in the wizard user interface.
You are unable to get the initial install command to run.
If your DataNodes are incorrectly configured, the smoke tests fail and you get this error message in the DataNode logs:
DisallowedDataNodeException org.apache.hadoop.hdfs.server.protocol. DisallowedDatanodeException
If you boot your Hadoop DataNodes with/as a ramdisk, you must disable the free space check for yum before doing the install. If you do not disable the free space check, yum will fail with the following error:
Fail: Execution of '/usr/bin/yum -d 0 -e 0 -y install unzip' returned 1. Error Downloading Packages: unzip-6.0-1.el6.x86_64: Insufficient space in download directory /var/cache/yum/x86_64/6/base/packages * free 0 * needed 149 k
You are unable to monitor or manage a service in Ambari Web when you have created a customized service user name with a hyphen, for example, hdfs-user
.