I'm trying to install Cloudera Manager 4.7.1 and CDH 4.4 on a fresh Hadoop
cluster, using method A (parcels) but a local parcel repository. This is
because my employer has a strict policy against letting certain production
servers connect to the larger Internet. I have the RPMs in the Cloudera
Manager RPM repository installed in a mirror on our intranet, and the CDH
4.4 parcel copied to /opt/cloudera/parcel-repo on the server which will
host Cloudera Manager. The initial install of the Manager went fine, and I
was able to hit port 7180 and begin the wizard to install CDH.
The problem is that when installing the parcel out to the nodes, it fails
because the installer's needlessly trying to go out to the Internet. It
appears to be trying to install the JDK (not necessary; we've already
installed it), and adding the cloudera manager yum repository to do it.
When yum tries to refresh the metadata for the CM yum repo, it fails and
treats that as a fatal error. (error message below)
Is there a way to either:
1. Have the CM skip Java installation, since it's not necessary
2. Override the yum repository that the CM will look for the JDK, and any
other package it needs? There should never be a case where we need the real
I can give up on the parcel approach and install the CDH 4.4 RPMs myself
(approach B), but I like the idea of rolling restart upgrades so I'd like
the keep the parcel approach if I can.
*BEGIN sudo yum info jdk *
Loaded plugins: fastestmirror, rhnplugin, security
Loading mirror speeds from cached hostfile
[Errno 12] Timeout on
(28, 'connect() timed out!')
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository:
cloudera-manager. Please verify its path and try again
*END (1) *
remote package jdk is not available, giving up
waiting for rollback request
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.