Ambari Troubleshooting Guide
Copyright © 2012-2016 Hortonworks, Inc.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
2016-11-09
Abstract
The Hortonworks Data Platform, powered by Apache Hadoop, is a massively scalable and 100% open source platform for storing, processing and analyzing large volumes of data. It is designed to deal with data from many sources and formats in a very quick, easy and cost-effective manner. The Hortonworks Data Platform consists of the essential set of Apache Hadoop projects including MapReduce, Hadoop Distributed File System (HDFS), HCatalog, Pig, Hive, HBase, ZooKeeper and Ambari. Hortonworks is the major contributor of code and patches to many of these projects. These projects have been integrated and tested as part of the Hortonworks Data Platform release process and installation and configuration tools have also been included.
Unlike other providers of platforms built using Apache Hadoop, Hortonworks contributes 100% of our code back to the Apache Software Foundation. The Hortonworks Data Platform is Apache-licensed and completely open source. We sell only expert technical support, training and partner-enablement services. All of our technology is, and will remain free and open source. Please visit the Hortonworks Data Platform page for more information on Hortonworks technology. For more information on Hortonworks services, please visit either the Support or Training page. Feel free to Contact Us directly to discuss your specific needs.
Contents
- 1. Troubleshooting Ambari Deployments
- Reviewing Ambari Log Files
- Resolving Ambari Install and Setup Problems
- Problem: Browser crashed before Install Wizard completes
- Problem: Install Wizard reports that the cluster install has failed
- Problem: Ambari Agents May Fail to Register with Ambari Server.
- Problem: The “yum install ambari-server” Command Fails
- Problem: HDFS Smoke Test Fails
- Problem: yum Fails on Free Disk Space Check
- Problem: Ambari Agents fail to register during the Confirm Host step
- Resolving Cluster Deployment Problems
- Problem: Trouble Starting Ambari on System Reboot
- Problem: Metrics and Host information display incorrectly in Ambari Web
- Problem: On SUSE 11 Ambari Agent crashes within the first 24 hours
- Problem: Attempting to Start HBase REST server causes either REST server or Ambari Web to fail
- Problem: Multiple Ambari Agent processes are running, causing re-register
- Problem: Ambari stops MySQL database during deployment, causing Ambari Server to crash.
- Problem: Cluster Install Fails with Groupmod Error
- Problem: Host registration fails during Agent bootstrap on SLES due to timeout.
- Problem: Host Check Fails if Transparent Huge Pages (THP) is not disabled.
- Problem: DataNode Fails to Install on RHEL/CentOS 7.
- Problem: When running Ambari Server as non-root, kadmin couldn't open log file.
- Problem: Adding client-only services does not automatically install component dependencies.
- Problem: Automatic Agent Registration with SSH fails for a non-root configuration.
- Resolving Cluster Upgrade Problems
- Problem: Versions tab does not show in Ambari Web.
- Problem: YARN Service Checks Fail and ResourceManager fails to start
- Problem: After HDP 2.2 -> 2.3 Manual Upgrade, Ambari alerts service flags Kafka Broker down.
- Problem: Ranger Admin UI does not function after upgrading HDP from 2.2 to 2.3
- Problem: Rolling or Express Upgrade fails while stopping HBase RegionServers
- Resolving General Problems
- Problem: When installing HDP 2.3.0 or 2.3.2, YARN ATS fails to start.
- Problem: After upgrading to Ambari 2.2, you receive File Does Not Exist alerts.
- During Enable Kerberos, the Check Kerberos operation fails.
- Problem: Hive developers may encounter an exception error message during Hive Service Check
- Problem: API calls for PUT, POST, DELETE respond with a "400 - Bad Request"
- Problem: Ambari is checking disk full on non-local disks; causing a high number of auto-mounted home directories
- Problem: Ambari Web shows Storm summary values as N/A in a Kerberized cluster
- Problem: kadmin running Ambari Server as non-root, cannot open log file.
- Problem: After changing NameNode RPC port, Ambari shows both NameNodes as standby.