Local Yum software source installation Cloudera Manager 5

local Yum software source installation Cloudera Manager 5

Cloudera Manager 5 (hereinafter referred to as cm) by default online installation, to the Internet or network is not easy to bring users inconvenience, due to network problems, repeated failure of the frustration, so that the first learning CDH users really experience the beginning of everything difficult. This article explains that in the CentOS 6 environment to build the local Yum software source, the local area network user in completely does not connect the Internet The situation, completes the CM the installation. Let the user who installed CM experience all the way next, then finish the smooth feeling, speed is the user's first experience.

first, build cm's local yum software source

CM's online documentation outlines how to build local yum, see: Creating and Using a native Package Repository, due to the different operating systems and CM versions, the description is not detailed, the following CentOS6.5 and The CM5.0.2 version of the local Yum software source is described as a setup step. 1. Preparation work

To turn off the firewall:

[root@localhost soft]# service iptables stop
iptables:setting chains to policy Accept:filter          [  OK  ]
  iptables:flushing firewall rules:                         [  OK  ]
iptables:unloading modules:                               [  OK  ]

Permanently shut down the firewall, you can use: Chkconfig iptables off

Close SELinux:

Modify:/etc/selinux/config
selinux=disabled
After modification, restart the machine.

2. Install Apache httpd Web server

Check for the existence of the HTTPD service:

[Root@localhost soft]# service httpd status

If it does not exist, install it with the following command:

Yum Install httpd

CentOS6 the httpd is installed by default, start:

[root@localhost soft]# Service httpd start
starting httpd:httpd:Could not reliably determine the server ' s fully qual ified domain name, using Localhost.localdomain for ServerName
                                                           [  OK  ]

The information above is not heeded. Add httpd to the startup list: Chkconfig httpd on httpd commonly used commands are as follows for reference:

Start command: Service httpd start
Shutdown command: Service httpd stop restart
command: Service httpd restart
View Status: Service httpd status

3. Download cm Resource Pack

To the CM resource page: http://archive-primary.cloudera.com/cm5/repo-as-tarball/5.0.2/Download the resource bundle, and the corresponding CentOS resource bundle is:

	cm5.0.2-centos6.tar.gz	11-jun-2014 18:12	517M	 

This is the compressed package, which contains the RPM files needed during the CM installation process, in addition to the PostgreSQL database installation files. 4. Publish cm Resource file

Unpack the resource bundle:

[Root@localhost cloudera]# Pwd/home/soft/cloudera [root@localhost cloudera]# ll Total 529076-rw-r--r--. 
1 root 541768507 June 09:14 cm5.0.2-centos6.tar.gz [root@localhost cloudera]# tar-zxvf cm5.0.2-centos6.tar.gz-cm/ Cm/cloudera-manager.repo CM/5 cm/5.0.2/cm/5.0.2/mirrors CM/5.0.2/REPODATA/CM/5.0.2/REPODATA/OTHER.XML.GZ.ASC cm/ 5.0.2/repodata/filelists.xml.gz CM/5.0.2/REPODATA/PRIMARY.XML.GZ.ASC Cm/5.0.2/repodata/repomd.xml cm/5.0.2/ repodata/other.xml.gz CM/5.0.2/REPODATA/REPOMD.XML.ASC cm/5.0.2/repodata/primary.xml.gz cm/5.0.2/repodata/ FILELISTS.XML.GZ.ASC cm/5.0.2/rpms/cm/5.0.2/rpms/x86_64/cm/5.0.2/rpms/x86_64/ cloudera-manager-daemons-5.0.2-1.cm502.p0.297.el6.x86_64.rpm cm/5.0.2/rpms/x86_64/ enterprise-debuginfo-5.0.2-1.cm502.p0.297.el6.x86_64.rpm cm/5.0.2/rpms/x86_64/ cloudera-manager-server-db-2-5.0.2-1.cm502.p0.297.el6.x86_64.rpm cm/5.0.2/rpms/x86_64/ cloudera-manager-server-5.0.2-1.cm502.p0.297.el6.x86_64.rpm cm/5.0.2/rpms/x86_64/ Cloudera-manager-agent-5.0.2-1.cm502.p0.297.el6.x86_64.rpm cm/5.0.2/rpms/x86_64/oracle-j2sdk1.7-1.7.0+update45-1.x86_64.rpm cm/5.0.2/RPMS/x86_64/
jdk-6u31-linux-amd64.rpm Cm/5.0.2/rpms/noarch/cm/rpm-gpg-key-cloudera [root@localhost cloudera]# ll Total 529080 Drwxrwxr-x. 3 1106 592 4096 June 11:08 Cm-rw-r--r--.  1 root 541768507 June 09:14 cm5.0.2-centos6.tar.gz [root@localhost cloudera]#

Move the extracted cm folder to the Web directory and set the permissions:

[Root@localhost html]# pwd
/var/www/html
[root@localhost html]# mkdir-p] cm5/redhat/6/x86_64
[ Root@localhost html]# cd cm5/redhat/6/x86_64
[root@localhost x86_64]# mv/home/soft/cloudera/cm.
[root@localhost x86_64]# chmod-r Ugo+rx cm

Access http://

At this point, the CM resource file within the LAN has been published, the following modifications are done at the client, that is, the machine that installs CM, and of course, the machine that holds the CM resource files can also install cm. second, offline installation Cloudera Manager 5 1. Installation PostgreSQL

It is sometimes reported as an error when installing cm Offline:

Resolving dependencies
--> Running transaction Check
---> Package cloudera-manager-server-db-2.x86_64 0:5.0.2-1.CM502.P0.297.EL6 is installed
--> processing Dependency:postgresql-server >= for 8.4 loudera-manager-server-db-2-5.0.2-1.cm502.p0.297.el6.x86_64
--> finished Dependency resolution
Error: Package:cloudera-manager-server-db-2-5.0.2-1.cm502.p0.297.el6.x86_64 (Cloudera-manager)
           Requires: Postgresql-server >= 8.4 You
 could try using--skip-broken to work around the problem you
 could try Running:rp M-va--nofiles--nodigest

This is due to the CM dependent PostgreSQL, the need to install PostgreSQL on the machine, if it is installed online, automatically installed in Yum mode, because it is offline, can not automatically install PostgreSQL.

Check to see if the PostgreSQL is installed:

[Root@localhost postgresql84]# Rpm-qa|grep Postgres

If it is already installed, but the version is less than 8.4, the RPM-E uninstall is used.

The following is the RPM installation of PostgreSQL, first to http://yum.postgresql.org/8.4/redhat/rhel-6-x86_64/repoview/download postgresql8.4 package, you need three packages:

[Root@localhost postgresql84]# ll Total
4532
-rw-r--r--1 root  898392 June 15 01:10 postgresql84-8.4.21-1pgdg.rhel6.x86_64.rpm
-rw-r--r--1 root  180396 June 15 01:10 postgresql84-libs-8.4.21-1pgdg.rhel6.x86_64.rpm
-rw-r--r--1 root 3552400 June 15 01:10 postgresql84-server-8.4.21-1pgdg.rhel6.x86_64.rpm
[Root@localhost postgresql84]# 

Install PostgreSQL, note the order of installation:

[Root@localhost postgresql84]# RPM-IVH postgresql84-libs-8.4.21-1pgdg.rhel6.x86_64.rpm Warning:                Postgresql84-libs-8.4.21-1pgdg.rhel6.x86_64.rpm:header V4 dsa/sha1 Signature, key ID 442df0f8:nokey Preparing ... ########################################### [100%] 1:postgresql84-libs ################################### ######## [100%] [root@localhost postgresql84]# rpm-ivh postgresql84-8.4.21-1pgdg.rhel6.x86_64.rpm Warning:                Postgresql84-8.4.21-1pgdg.rhel6.x86_64.rpm:header V4 dsa/sha1 Signature, key ID 442df0f8:nokey preparing ... ########################################### [100%] 1:postgresql84 ######################################## ### [100%] [root@localhost postgresql84]# rpm-ivh postgresql84-server-8.4.21-1pgdg.rhel6.x86_64.rpm Warning:                Postgresql84-server-8.4.21-1pgdg.rhel6.x86_64.rpm:header V4 dsa/sha1 Signature, key ID 442df0f8:nokey Preparing ... ########################################### [100%] 1:postgreSql84-server ########################################### [100%] [root@localhost postgresql84]#  

PostgreSQL Package description for reference:
PostgreSQL contains a number of different packages, including Third-party libraries, which are typically installed with the most important packages (most of the application requirements are met). These packages are as follows:
PostgreSQL-Client class library and binary files
Postgresql-server-The core database server
Postgresql-contrib-Additional Supply components
Postgresql-devel-class libraries and header files developed by the User C language
PGADMIN3-Database Imaging Management tool, third edition 2, modify the client configuration so that it can find resource files

Shut down the firewall and SELinux on the client machine, see the description in the preparation process.

Create a new software source configuration file named Myrepo.repo, which reads as follows:

[Myrepo]
Name=myrepo
baseurl=http://
Where 
[Root@localhost yum.repos.d]# pwd
/etc/yum.repos.d
[root@localhost yum.repos.d]# ll Total
4
- rw-r--r--1 root June 21:14 Myrepo.repo
[root@localhost yum.repos.d]# 

Setting the source of the software is not enough, but also uninstall some profiles from the Internet, although the software source contains all the required files, modify the/etc/hosts, add at the end:

Where  
3, download CM5 installation files

Download from http://archive-primary.cloudera.com/cm5/installer/5.0.2.13/:

Cloudera-manager-installer.bin	11-jun-2014 18:07	499K	 
The boot file is actually installed, and the RPM packages needed during installation are dynamically downloaded during installation.
4. Installation CM5

To add executable permissions to Cloudera-manager-installer.bin:

[Root@localhost cloudera]# chmod +x cloudera-manager-installer.bin
 
To install:

[Root@localhost cloudera]#./cloudera-manager-installer.bin 
Pop-up installation graphical interface, all the way next, accept on it, and finally appear the following prompt box, let you visit the http://localhost:7180/, indicating that the installation has been successful.




C. Login cm Admin page

Using both username and password for admin login http://localhost:7180/, the interface is as follows:





Login cm Admin page, carry on the related operation, after the article detailed description impala, spark the off-line installment method.

Original works, reproduced please indicate the source: http://blog.csdn.net/yangzhaohui168/article/details/30118175