CDH use of cm 5.3.x installation

Preface:CmFull nameCloudera Manager,Clouderadevelop the company's products. Its main function is toCDHmonitoring of the cluster, greatly improving the nativeApachehadoopinstallation, configuration complexity, and the need to use third-party open source monitoring tools for many problems. Among them,CDHis aClouderaThe company's open source products, can not rely onCmStandalone installation. Cmhave aFreeversion that provides60The free term for advanced features that you can use in the Premium edition. This articleCminstallation based onCentOS 6.5, there may be subtle differences before each system version, which the reader should consult on its own, and theoreticallyRed HatSystem. First, System preparation 1. system installation This adoption of the system version of CentOS 6.5, the system part is relatively simple, the specific installation of the tutorial this article does not do a detailed introduction, the latter to write a separate installation of the CentOS system tutorial. 2. System Configuration A) user-created CM installation can be installed with ordinary users, the system can be installed during the installation of ordinary users or in the installation of the following command to add (add a custom user name within the angle brackets). Create user # useradd < user name > Change Password # passwd < user name > b) Turn off SELinux The installation of CM must close SELinux, the shutdown method is as follows: # Vi/etc/selinux/config Change SELinux to Disabled c) Turn off the firewall CM installation easy to shut down the firewall, firewall open may cause the CM related port can not be accessed. The closing method is as follows: Temporary shutdown: View off status # Service Iptables Status Shutting down the firewall # Serviceiptables Stop Configure power-on shutdown firewall: # vi/etc/rc.local Permanently closed: Viewing the startup level # chkconfig--list iptables turn off all boot levels # chkconfig Iptables off   Note: The actual cluster may be closed using the above method, the firewall will still open automatically, you need to check the cluster environment for a firewall check mechanism. d) SSH free key configuration (not required) First generate a pair of private keys and public keys, as follows: # ssh-keygen-t Rsa-p '-F ~/.ssh/id_rsa # Ssh-copy-id <IP address > (IP address is your specific and who is exempt from key, you have to set and self-free key) e) Configure Sudo functionality (not required) Execute the following command: # Visudo or #vi/etc/sudoers. Add the following ( Add a custom user name inside the angle brackets ): <user> all= (All) Nopasswd:all 3. Dependent Software Services the CM installation relies on the PostgreSQL database (which can be changed to another database) and some other service components that can be selected for the software during operating system installation and can be later installed. You can download the installation package for installation, or you can install it using the Yum method, which requires the following components: Yum-y Install Postgresql-server Yum-y Install PostgreSQL Yum-y Install httpd Yum-y Install Perl Yum-y Install Bind-utils Yum-y Install Libxslt Yum-y Install Cyrus-sasl-gssapi Yum-y Install REDHAT-LSB Yum-y Install Cyrus-sasl-plain Yum-y Install Portmap Yum-y Install fuse Yum-y Install Fuse-libs Yum-y Install NC Yum-yinstall Python-setuptools Yum-y installopenssh-clients (when SSH is not available) Note: The/etc/yum.repos.d/directory requires configuration files when installing with Yum (no self-Baidu). File:///C:/Users/WANGLI~1/AppData/Local/Temp/OICE_F1CC53DF-AFC8-4B3A-B9F7-A2FBB9833C1E.0/msohtmlclip1/01/clip_image008.png Second, media preparation 1, installation mode selection A) Tar package installation (this article does not introduce) b) RPM Package mode installation This article chooses the RPM package method to install, downloads the corresponding rpm package and the corresponding directory structure, accesses the local through the Httpd-apache way Yum source for installation. 2,cm5.3.x download The tar package is as follows: HTTP://ARCHIVE-PRIMARY.CLOUDERA.COM/CM5/CM/5/(select version based on OS version) RPM Package: http://archive.cloudera.com/cm5/redhat/6/x86_64/cm/(CentOS6.5 system Select redhat version ) Installing the Yum mode also requires downloading a bin file with the following address: http://archive.cloudera.com/cm5/installer/5.3.2/( directory name corresponds to CM version ) RPM package download need to keep the corresponding directory structure in the Web page, put in the/var/www/html/ directory, as follows: File:///C:/Users/WANGLI~1/AppData/Local/Temp/OICE_F1CC53DF-AFC8-4B3A-B9F7-A2FBB9833C1E.0/msohtmlclip1/01/clip_image010.png Third, configure the Yum source Configure local yum source Under/etc/yum.repos.d/, create the Cloudera-manager.repo configuration file with the following content: [Cloudera-manager] Name = Cloudera Manager, Version 5.3.2 BaseURL = HTTP://IP Address/cm5.3.2 Gpgcheck = 0 Note: IP addresses are recommended to use intranet IP to improve transmission speed. iv. installation of CM1. Service start-up Start the HTTP service and paste the BaseURL address of the repo file into the browser to verify that it can be accessed via HTTP. Start the HTTP service # service httpd Start View HTTP Service Status # Service HTTPD Status File:///C:/Users/WANGLI~1/AppData/Local/Temp/OICE_F1CC53DF-AFC8-4B3A-B9F7-A2FBB9833C1E.0/msohtmlclip1/01/clip_image012.png 2. Start the installation Any directory to execute the Cloudera-manager-installer.bin file, follow the continuous selection of the Next button:     File:///C:/Users/WANGLI~1/AppData/Local/Temp/OICE_F1CC53DF-AFC8-4B3A-B9F7-A2FBB9833C1E.0/msohtmlclip1/01/clip_image014.png File:///C:/Users/WANGLI~1/AppData/Local/Temp/OICE_F1CC53DF-AFC8-4B3A-B9F7-A2FBB9833C1E.0/msohtmlclip1/01/clip_image016.png Still continue next, then yes File:///C:/Users/WANGLI~1/AppData/Local/Temp/OICE_F1CC53DF-AFC8-4B3A-B9F7-A2FBB9833C1E.0/msohtmlclip1/01/clip_image018.png File:///C:/Users/WANGLI~1/AppData/Local/Temp/OICE_F1CC53DF-AFC8-4B3A-B9F7-A2FBB9833C1E.0/msohtmlclip1/01/clip_image020.png The following progress bar appears, waiting until 100% File:///C:/Users/WANGLI~1/AppData/Local/Temp/OICE_F1CC53DF-AFC8-4B3A-B9F7-A2FBB9833C1E.0/msohtmlclip1/01/clip_image022.png File:///C:/Users/WANGLI~1/AppData/Local/Temp/OICE_F1CC53DF-AFC8-4B3A-B9F7-A2FBB9833C1E.0/msohtmlclip1/01/clip_image024.png Finally, the following interface appears, indicating that the installation is complete. File:///C:/Users/WANGLI~1/AppData/Local/Temp/OICE_F1CC53DF-AFC8-4B3A-B9F7-A2FBB9833C1E.0/msohtmlclip1/01/clip_image026.png Click OK, the browser access HTTP://IP address: 7180/access, password and username are admin (can be modified after login) 3. Error location During the installation process, you can see the error log in the corresponding error log on the installation prompt and check the corresponding error logs. Regardless of whether the installation is successful, the. rpmnew file is added to the corresponding/ETC/YUM.REPOS.D directory, and this file is generally linked to the remote warehouse address of the download cm, which is removed after continuing the retry installation. File:///C:/Users/WANGLI~1/AppData/Local/Temp/OICE_F1CC53DF-AFC8-4B3A-B9F7-A2FBB9833C1E.0/msohtmlclip1/01/clip_image028.png Five, installation process precautions Common causes of failures during installation are: 1, SELinux out of the open state, set the disabled does not take effect 2, firewall out of the open state 3, PostgreSQL database is not installed or service does not start 4, httpd service does not open or configured BaseURL address is not available For more information, please visit: http://bbs.superwu.cn Focus on the two-dimensional code of Superman Academy:

CDH use of cm 5.3.x installation