FAQ
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
OR
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
CM repo.

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.

Thanks,

Geoffrey Jacoby

Error Message:
*BEGIN sudo yum info jdk *
Loaded plugins: fastestmirror, rhnplugin, security
Loading mirror speeds from cached hostfile
http://archive.cloudera.com/cm4/redhat/6/x86_64/cm/4.7.1/repodata/repomd.xml:
[Errno 12] Timeout on
http://archive.cloudera.com/cm4/redhat/6/x86_64/cm/4.7.1/repodata/repomd.xml:
(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 scm-users+unsubscribe@cloudera.org.

Search Discussions

  • Philip Zeyliger at Sep 20, 2013 at 4:18 pm
    Hi Geoffrey,

    You can still use parcels. What you want to do is install the CM server
    itself from packages (this is documented in "Path B" and is roughly "yum
    install cloudera-manager-daemons cloudera-manager-server-db
    cloudera-manager-server; service cloudera-scm-server-db start; service
    cloudera-scm-server start". (The scm-installer.bin does that, and also
    installs the JDK, which you can do however you do it for other things.)
      Once there you can follow the wizard, specify custom repos, and be on your
    way. Parcels will work with this setup.

    I recently drew up a diagram of the admittedly many paths you can get
    through installation.
    https://dl.dropboxusercontent.com/u/413065/InstallationPathsOfCM.pdf is the
    link.

    Hope this helps!

    -- Philip



    On Thu, Sep 19, 2013 at 12:51 PM, Geoffrey Jacoby wrote:

    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
    OR
    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
    CM repo.

    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.

    Thanks,

    Geoffrey Jacoby

    Error Message:
    *BEGIN sudo yum info jdk *
    Loaded plugins: fastestmirror, rhnplugin, security
    Loading mirror speeds from cached hostfile

    http://archive.cloudera.com/cm4/redhat/6/x86_64/cm/4.7.1/repodata/repomd.xml:
    [Errno 12] Timeout on
    http://archive.cloudera.com/cm4/redhat/6/x86_64/cm/4.7.1/repodata/repomd.xml:
    (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 scm-users+unsubscribe@cloudera.org.
    To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedSep 19, '13 at 7:51p
activeSep 20, '13 at 4:18p
posts2
users2
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase