Unable to install CM using local repository

[#1]

Hello,

I am trying to install CM 5.0.0 using Local repository by following the installation guide provided by Cloudera.

Steps taken:

1. Created permanent local repository following the steps provided in the guide.

2. Initiated CM install via cloudera-manager-installer.bin

However, the installer is unable to find the cloudera-manager-server-db package as per the logs created in Cloudera Manager Installer folder under /var/logs

I tried to install cloudera-manager-server-db explicitly using below command:

yum install cloudera-manager-server-db

However, I receive the same error.

Found that the package name in the repo I downloaded is cloudera-manager-server-db-2-5.0.0-1.cm500.p0.215.el6.x86_64. Tried below command

yum install cloudera-manager-server-db-2-5.0.0-1.cm500.p0.215.el6.x86_64

This time it was able to find the package and proceed.

Is there something I have not configured while creating repo or is there a way to direct the CM installation to look for complete name of package. I tried renaming the package to cloudera-manager-server-db, but it did not work.

Please advise.

Regards,

snm102

[#2]

> I tried to install cloudera-manager-server-db explicitly using below command:

> yum install cloudera-manager-server-db

I believe this is a know issue related to our packaging since 5.0.0b2  

- The name of the Cloudera Manager embedded database package has changed from cloudera-manager-server-db to cloudera-manager-server-db-2. For details, read the upgrade and install topics for your OS [1]

> Is there something I have not configured while creating repo or is there a way to direct the CM installation to look for complete name of package. I tried renaming the package to cloudera-manager-server-db, but it did not work.

You mentioned that you were able to find the package and proceed, did CM embedded db not start-up after the installation and what is your current status of CM?

[1] What's Changed in Cloudera Manager 5.0.0 Beta 2

http://www.cloudera.com/content/www/en-us/documentation/enterprise/5-3-x/topics/cm_rn_new_changed_fe...

[#3]

Thank you for the response Michalis.

No it did not start by itself.

Also, I tried to install CM again with Embedded database already installed, this time it failed on the next step after Embedded database installation.

For now I have cleaned my VMs and CM is not installed neither the embedded database.

Thanks

snm1523

[#4 · Accepted solution]

Let me rephrase what you have done so far, just to confirm I understood your issue correctly.

You have: 

1. Created permanent local repository following the steps provided in the guide.

2. Initiated CM install via cloudera-manager-installer.bin

And based on the above the installation did not succeed.

So, for now you have cleaned your VMs and CM is not installed neither the embedded database.

From what I've gathered you have .el6. (RHEL/Centos 6) OS, and you're trying to install CM 5.0.0. and using Path A installation method.

As we're trying to discourage people from using Path A installation. A suggested workaround would be;

In a fresh environment and assuming you've logged in as root (or you can prefix the commands with sudo), without configuring .repo file in /etc/yum.repos.d/

1. change into a working dir to download the rpm's

# cd /working_dir/

2. download the .rpm for CM 5.0.0. from Cloudera repo

# wget -r --no-parent -nc -nd --reject "index.html*" http://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5.0.0/RPMS/x86_64/

3. confirm if you have the right set or .rpm's

# ls -lt 

...

-rw-r--r-- 1 root root 71204325 Apr 1 2014 jdk-6u31-linux-amd64.rpm
-rw-r--r-- 1 root root 8180 Apr 1 2014 cloudera-manager-server-5.0.0-1.cm500.p0.215.el6.x86_64.rpm
-rw-r--r-- 1 root root 683432 Apr 1 2014 enterprise-debuginfo-5.0.0-1.cm500.p0.215.el6.x86_64.rpm
-rw-r--r-- 1 root root 328227356 Apr 1 2014 cloudera-manager-daemons-5.0.0-1.cm500.p0.215.el6.x86_64.rpm
-rw-r--r-- 1 root root 137780131 Apr 1 2014 oracle-j2sdk1.7-1.7.0+update45-1.x86_64.rpm
-rw-r--r-- 1 root root 9884 Apr 1 2014 cloudera-manager-server-db-2-5.0.0-1.cm500.p0.215.el6.x86_64.rpm
-rw-r--r-- 1 root root 3844576 Apr 1 2014 cloudera-manager-agent-5.0.0-1.cm500.p0.215.el6.x86_64.rpm

...

4. Install the packages based on their order of dependencies. 

# yum install -y oracle-j2sdk* cloudera-manager-daemons* cloudera-manager-server* cloudera-manager-server-db-2*

Note: for JDK 1.7 use oracle-j2sdk* and for JDK 1.6 replace oracle-j2sdk* with jdk-6u31*

The installation should complete with the following stdout

...

Running Transaction
Installing : postgresql-libs-8.4.20-3.el6_6.x86_64 1/7
Installing : postgresql-8.4.20-3.el6_6.x86_64 2/7
Installing : postgresql-server-8.4.20-3.el6_6.x86_64 3/7
Installing : cloudera-manager-daemons-5.0.0-1.cm500.p0.215.el6.x86_64 4/7
warning: user cloudera-scm does not exist - using root
warning: group cloudera-scm does not exist - using root
Installing : cloudera-manager-server-5.0.0-1.cm500.p0.215.el6.x86_64 5/7
Installing : cloudera-manager-server-db-2-5.0.0-1.cm500.p0.215.el6.x86_64 6/7
Installing : oracle-j2sdk1.7-1.7.0+update45-1.x86_64 7/7
Verifying : cloudera-manager-server-5.0.0-1.cm500.p0.215.el6.x86_64 1/7
Verifying : cloudera-manager-daemons-5.0.0-1.cm500.p0.215.el6.x86_64 2/7
Verifying : postgresql-libs-8.4.20-3.el6_6.x86_64 3/7
Verifying : oracle-j2sdk1.7-1.7.0+update45-1.x86_64 4/7
Verifying : postgresql-8.4.20-3.el6_6.x86_64 5/7
Verifying : cloudera-manager-server-db-2-5.0.0-1.cm500.p0.215.el6.x86_64 6/7
Verifying : postgresql-server-8.4.20-3.el6_6.x86_64 7/7

Installed:
cloudera-manager-daemons.x86_64 0:5.0.0-1.cm500.p0.215.el6
cloudera-manager-server.x86_64 0:5.0.0-1.cm500.p0.215.el6
cloudera-manager-server-db-2.x86_64 0:5.0.0-1.cm500.p0.215.el6
oracle-j2sdk1.7.x86_64 0:1.7.0+update45-1

Dependency Installed:
postgresql.x86_64 0:8.4.20-3.el6_6 postgresql-libs.x86_64 0:8.4.20-3.el6_6
postgresql-server.x86_64 0:8.4.20-3.el6_6

Complete!

...

Let me know if this helps.

[#5]

Thank you for the response Michalis.

I have got tied up with other tasks currently and would have to work on this over the weekend. Will perform the suggested steps and post back the results.

Just to confirm, once the installation is completed I should be able to login to CM console, correct.

Thanks

Snm1523

[#6]

The above mentioned workaround is using Path B manual installation, the next step is to start the services

1a. Check the status of the embedded DB

# service cloudera-scm-server-db status

1b. Start the service if necesary

# service cloudera-scm-server-db start

2a.Check the status of the Cloudera Manager Server  

# service cloudera-scm-server status

1b. Start the service if necesary

# service cloudera-scm-server start

Since it's initial start, it might take a while for the Cloudera Manager Server to intialise. 

3. On the node where you have installed Cloudera Manager Server,

use netstat command to check if cloudera-scm-server has started listening on port 7180 - only then you should be

able to login to CM console

# netstat -lntup | grep 7180
tcp 0 0 0.0.0.0:7180 0.0.0.0:* LISTEN 14613/java

Have fun.