5.8. Check umask Value
Sidebar
Prev
|
Up
|
Next
Docs
Hortonworks Data Platform
5.8. Check umask Value
Make sure umask is set to 022.
Legal notices
Contents
Search
1. Getting Ready to Install
1. Understand the Basics
2. Meet Minimum System Requirements
2.1. Hardware Recommendations
2.2. Operating Systems Requirements
2.3. Browser Requirements
2.4. Software Requirements
2.5. Database Requirements
3. Decide on Deployment Type
4. Collect Information
5. Prepare the Environment
5.1. Check Existing Installs
5.2. Set Up Password-less SSH
5.3. Enable NTP on the Cluster and on the Browser Host
5.4. Check DNS
5.4.1. Edit the Host File
5.4.2. Set the Hostname
5.4.3. Edit the Network Configuration File
5.5. Disable SELinux
5.6. Disable iptables
5.7. Disable PackageKit
5.8. Check umask Value
6. Optional: Configure the Local Repositories
2. Running the Installer
1. Set Up the Bits
1.1. RHEL/CentOS/Oracle Linux 5.x
1.2. RHEL/CentOS/Oracle Linux 6.x
1.3. SLES 11
2. Set Up the Server
2.1. Setup Options
3. Optional: Set Up LDAP or Active Directory Authentication
4. Optional: Set Up HTTPS for Ambari Web
5. Optional: Set Up HTTPS for Ganglia and Nagios
5.1. Set Up Ganglia
5.2. Set Up Nagios
6. Optional: Encrypt Database and LDAP Passwords
6.1. Reset Encryption
6.1.1. Remove Encryption Entirely
6.1.2. Change the Current Master Key
7. Optional: Set Up Two-Way SSL Between Ambari Server and Ambari Agents
8. Optional: Change the Ambari Server Port
9. Start the Ambari Server
3. Installing, Configuring, and Deploying the Cluster
1. Log into Apache Ambari
2. Welcome
3. Select Stack
4. Install Options
5. Confirm Hosts
6. Choose Services
7. Assign Masters
8. Assign Slaves and Clients
9. Customize Services
9.1. Service Users and Groups
9.2. Properties That Depend on Service Usernames/Groups
9.3. Recommended Memory Configurations for the MapReduce Service
10. Review
11. Install, Start and Test
12. Summary
4. Troubleshooting Ambari Deployments
1. Getting the Logs
2. Quick Checks
3. Specific Issues
3.1. Problem: Browser crashed before Install Wizard completed
3.1.1. Solution
3.2. Problem: Install Wizard reports that the cluster install has failed
3.2.1. Solution
3.3. Problem: “Unable to create new native thread” exceptions in HDFS DataNode logs or those of any system daemon
3.3.1. Solution:
3.4. Problem: The “yum install ambari-server” Command Fails
3.4.1. Solution:
3.5. Problem: HDFS Smoke Test Fails
3.5.1. Solution:
3.6. Problem: The HCatalog Daemon Metastore Smoke Test Fails
3.6.1. Solution:
3.7. Problem: MySQL and Nagios fail to install on RightScale CentOS 5 images on EC2
3.7.1. Solution:
3.8. Problem: Trouble starting Ambari on system reboot
3.8.1. Solution:
3.9. Problem: Metrics and Host information display incorrectly in Ambari Web
3.9.1. Solution:
3.10. Problem: On SUSE 11 Ambari Agent crashes within the first 24 hours
3.10.1. Solution:
3.11. Problem: Attempting to Start HBase REST server causes either REST server or Ambari Web to fail
3.11.1. Solution
3.12. Problem: Multiple Ambari Agent processes are running, causing re-register
3.12.1. Solution
3.13. Problem: Some graphs do not show a complete hour of data until the cluster has been running for an hour
3.13.1. Solution
3.14. Problem: After performing a cluster install the Nagios server is not started
3.14.1. Solution
3.15. Problem: A service with a customized service user is not appearing properly in Ambari Web
3.15.1. Solution
3.16. Problem: Updated configuration changes are not pushed to client/gateway nodes
3.16.1. Solution
3.17. Problem: Trying to upgrade Ambari Server on SLES produces error
3.17.1. Solution
5. Appendix: Installing Ambari Agents Manually
1. RHEL/CentOS/Oracle Linux v. 5.x and 6.x
2. SLES
6. Appendix: Using Custom Hostnames
7. Appendix: Upgrading Operating Systems on an Ambari-based Hadoop Installation
8. Appendix: Upgrading Ambari to 1.2.5
9. Appendix: Upgrading the HDP Stack to 1.3.2
1. Preparing for the Upgrade
2. Setting Up the Ambari Repository
3. Upgrading Ambari
4. Upgrading the Stack (from 1.2.* to 1.3.2)
5. Upgrading the Stack (from 1.3.0 to 1.3.2)
10. Appendix: Configuring Ports
1. HDFS Ports
2. MapReduce Ports
3. Hive Ports
4. HBase Ports
5. WebHCat Port
6. Ganglia Ports
7. MySQL Port
8. Ambari Ports
9. Nagios Ports
11. Appendix: Moving the Ambari Server
1. Back up Current Data
2. Update Agents
3. Install the New Server and Populate the Databases
12. Appendix: Using Non-Default Databases
1. Hive/HCatalog
1.1. Troubleshooting Hive/HCatalog
1.1.1. Problem: Hive Metastore Install Fails Using Oracle
1.1.1.1. Soution
1.1.2. Problem: Install Warning when "Hive Check Execute" Fails Using Oracle
1.1.2.1. Soution
2. Oozie
2.1. Troubleshooting Oozie
2.1.1. Problem: Oozie Server Install Fails Using MySQL
2.1.1.1. Soution
2.1.2. Problem: Oozie Server Install Fails Using Oracle or MySQL
2.1.2.1. Soution
3. Ambari
3.1. Troubleshooting Ambari
3.1.1. Problem: Ambari Server Fails to Start: No Driver
3.1.1.1. Soution
3.1.2. Problem: Ambari Server Fails to Start: No Connection
3.1.2.1. Soution
3.1.3. Problem: Ambari Server Fails to Start: Bad Username
3.1.3.1. Soution
3.1.4. Problem: Ambari Server Fails to Start: No Schema
3.1.4.1. Soution
13. Setting Up Kerberos for Use with Ambari
1. Preparing Kerberos
1.1. Kerberos Overview
1.2. Installing and Configuring the KDC
1.3. Creating the Database
1.4. Starting the KDC
1.5. Installing and Configuring the Kerberos Clients
1.6. Creating Service Principals and Keytab Files for Hadoop
2. Configuring Hadoop
2.1. Configuration Overview
2.2. Creating Mappings Between Principals and UNIX Usernames
2.2.1. Creating Rules
2.2.2. Examples
2.3. Adding Security Information to Configuration Files
2.3.1. Configuring Secure HDFS and MapReduce
2.3.1.1. Setting DataNode User Privileges
2.3.1.2. Starting and Testing HDFS and MapReduce
2.3.2. Configuring Secure Oozie
2.3.3. Configuring Secure Hive
2.3.4. Configuring Secure WebHCat
2.3.5. Configuring Secure HBase and ZooKeeper
2.3.5.1. Configure the HBase Master
2.3.5.2. Create the JAAS Configuration Files
2.3.5.3. Start HBase and ZooKeeper Services
2.3.5.4. Configure Secure Client Side Access to HBase
2.3.5.5. Optional: Configure Client-Side Operation For Secure Operation - Thrift Gateway
2.3.5.6. Optional: Configure Client-Side Operation For Secure Operation - REST Gateway
2.3.5.7. Configure HBase for Access Control Lists (ACL)
2.4. Providing the jce-6 Security JAR Files
Search
Search Highlighter (On/Off)
