Reply
New Contributor
Posts: 7
Registered: ‎03-29-2017
Accepted Solution

Installation Failed: Installing Cloudera Manager 5 on EC2

To create my Hadoop cluster, I followed the instructions here:

    https://blog.insightdatascience.com/spinning-up-a-free-hadoop-cluster-step-by-step-c406d56bae42

and it seems to be working OK.

 

Now, I'm trying to install Cloudera Manger 5 using these instructions:

    http://www.cloudera.com/documentation/manager/5-1-x/Cloudera-Manager-Installation-Guide/cm5ig_instal...

 

and I get an error in step 5.i. Executing the Installer. I get the error:  "Refreshing repository metadata failed. See [...] log for details.  According to the log, there is an error fetching from    

    http://archive.cloudera.com/cm5/ubuntu/xenial/amd64/cm/dists/xenial-cm5/contrib/source/

Here is a screenshot of the error and log
screenshot of error and contents of log

 (https://www.dropbox.com/s/aiugul4findice2/Screenshot%202017-03-29%2006.28.38.png?dl=0)

Please help!

 

VY

 

Cloudera Employee
Posts: 116
Registered: ‎04-12-2016

Re: Installation Failed: Installing Cloudera Manager 5 on EC2

What is the operationg system you are trying to install on?   The error shows it is looking for files for Ubuntu16.04 (xenial) we haven't released CM for that O/S yet.

 

Tina

Posts: 957
Topics: 1
Kudos: 228
Solutions: 121
Registered: ‎04-22-2014

Re: Installation Failed: Installing Cloudera Manager 5 on EC2

Hi @hadoopuser2000,

 

Based on your screenshots, it appears you are attempting to install on an OS that is not yet supported (Xenial)

 

Currently, only Trusty and Precise Ubuntu are supported as noted here:

https://www.cloudera.com/documentation/enterprise/release-notes/topics/rn_consolidated_pcm.html#os51...

 

Trusty 14.04 - Long-Term Support (LTS)

Precise 12.04 - Long-Term Support (LTS)

 

When there is an attempt to download the xenial rpms from the Cloudera archive, that fails since there is no such directory or rpms.

 

Ubuntu 16.04 support is currently targeted for CM/CDH 5.11

 

-Ben

 

Ben

New Contributor
Posts: 7
Registered: ‎03-29-2017

Re: Installation Failed: Installing Cloudera Manager 5 on EC2

Hi,

 

Thank you for the answer, but I'm having a different problem now.

 

I've created another 4 instances of Ubuntu 14 and installed Hadoop. I've downloaded and run the Cloudera Manager Installer (as per http://www.cloudera.com/documentation/manager/5-1-x/Cloudera-Manager-Installation-Guide/cm5ig_instal...), but now the problem is that I can't seem to load "http://public hostname:7180". If I understand correctly, "public hostname" is where I enter the public dns of a node -- say, the namenode -- correct?

 

What am I doing wrong now?

 

Screenshot 2017-03-30 00.20.13.pngScreenshot 2017-03-30 00.20.18.png

 

New Contributor
Posts: 5
Registered: ‎08-09-2018

Re: Installation Failed: Installing Cloudera Manager 5 on EC2

I am trying to install by this same process

 

http://www.cloudera.com/documentation/manager/5-1-x/Cloudera-Manager-Installation-Guide/cm5ig_instal...

 

but getting this error

 

/var/log/cloudera-manager-installer/3.install-oracle-j2sdk1.7.log

----------------------------------
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
oracle-j2sdk1.7
0 upgraded, 1 newly installed, 0 to remove and 188 not upgraded.
Need to get 142 MB of archives.
After this operation, 292 MB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
oracle-j2sdk1.7
E: There are problems and -y was used without --force-yes

 

 

Server Information:

Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty

Posts: 957
Topics: 1
Kudos: 228
Solutions: 121
Registered: ‎04-22-2014

Re: Installation Failed: Installing Cloudera Manager 5 on EC2

@hadoopuser2000,

 

Are you still having trouble?  The screen shots indicate you need to uninstall before installing again, so I'd try that.

I wasn't clear how the screen shots were related to the problem connecting to CM.

 

First, make sure CM is running;

 

# netstat -nap |grep 7180

 

If you see that it is listening, make sure that you can connect to the host on which Cloudera Manager is installed from whatever client you are using to connect to Cloudera Manager.

By public address, the doc means that you should use whatever hostname will resolve to an IP that lets you connect to that host and port.

 

 

Announcements