Unable to proceed with Cloudera Manger isntallation, Issue with SDK installation

[#1]

Hi,

I am trying to setup a 3 node cluser using latest Cloudera Manger. I am getting error as:

Remote package oralce-j2sdk1.6 could not be installed, giving up.

I am using Debian 7.1 OS

[#2]

Hello,

The version of Java you are attempting to install is unsupported in CM 5.8.x.

http://www.cloudera.com/documentation/enterprise/release-notes/topics/rn_consolidated_pcm.html#pcm_j...

[#3]

Thanks for the reply, to clarify, I am not trying to do standalone installation of JAVA, it,s the cloudera manager which is trying to install it

[#4]

Hello,

When adding a host, Cloudera Manager will execute a script on the host you are adding.  The script will attempt to install various packages.  For legacy support, the 1.6 JDK is installed even though you will not be using it.  When you see the error regarding the jdk install, you should be able to click on a link to get the details to understand why it failed.

If you chose to use the same repository as Cloudera Manager, the install should succeed, but it could be that on your new host there is another OS repository that contains the "jdk" package.  If that is the case, remove that repo configuration temporarily for the install.

At the least, if you can share with us the error that occurs to cause the failure, we can help further.

[#5]

Hi, below is the text from details link after installation is failed:

Cluster Installation

Installation in progress.

0 of 3 host(s) completed successfully.

Installation failed on 3 host(s).

Hostname IP Address Progress Status

cdh5-1.vm	192.168.56.102		Uninstall | Details Installation failed.
cdh5-2.vm	192.168.56.103		Uninstall | Details Installation failed.
cdh5-3.vm	192.168.56.104		Uninstall | Details Installation failed.

Failed to install oracle-j2sdk1.6 package. (Failed Step)
(Current Step) Last Refreshed: Oct 4, 2016 10:38:42 PM PDT

/tmp/scm_prepare_node.aei1QB6j
using SSH_CLIENT to get the SCM hostname: 192.168.56.102 54289 22
opening logging file descriptor

Starting installation script... Acquiring installation lock...

BEGIN flock 4
END (0)

Detecting root privileges...

effective UID is 0

Detecting distribution...

BEGIN cat /etc/debian_version
END (0)
7.11

Detecting Cloudera Manager Server...

BEGIN host -t PTR 192.168.56.102
Host 102.56.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
END (1)
BEGIN which python
END (0)
BEGIN python -c 'import socket; import sys; s = socket.socket(socket.AF_INET); s.settimeout(5.0); s.connect((sys.argv[1], int(sys.argv[2]))); s.close();' 192.168.56.102 7182
/usr/bin/python
END (0)
BEGIN which wget
END (0)
/usr/bin/wget
BEGIN wget -qO- -T 1 -t 1 http://169.254.169.254/latest/meta-data/public-hostname && /bin/echo
END (4)

Installing package repositories...

validating format of repository file /tmp/scm_prepare_node.aei1QB6j/repos/debian_wheezy/cloudera-manager.list
installing repository file /tmp/scm_prepare_node.aei1QB6j/repos/debian_wheezy/cloudera-manager.list
repository file /tmp/scm_prepare_node.aei1QB6j/repos/debian_wheezy/cloudera-manager.list installed
BEGIN apt-key add /tmp/scm_prepare_node.aei1QB6j/archive.key
OK
END (0)

Refreshing package metadata...

BEGIN apt-get update
E: The method driver /usr/lib/apt/methods/https could not be found.
END (100)
BEGIN apt-get update
END (100)
E: The method driver /usr/lib/apt/methods/https could not be found.

Installing oracle-j2sdk1.6 package...

BEGIN dpkg -l oracle-j2sdk1.6 | grep -E '^ii[[:space:]]*oracle-j2sdk1.6[[:space:]]*'
dpkg-query: no packages found matching oracle-j2sdk1.6
END (1)
BEGIN apt-cache show oracle-j2sdk1.6
END (0)
Package: oracle-j2sdk1.6
Version: 1.6.0+update31
Architecture: amd64
Maintainer: Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
Installed-Size: 224994
Depends: libasound2 (>= 1.0.16), libc6 (>= 2.2.5), libx11-6, libxext6, libxi6, libxt6, libxtst6
Recommends: netbase, libgtk1.2, libstdc++5
Replaces: oracle-j2sdk1.6debian
Provides: j2re1.6, j2sdk1.6, java-browser-plugin, java-compiler, java-runtime, java-runtime-headless, java-sdk, java-virtual-machine, java2-compiler, java2-runtime, java2-runtime-headless, java2-sdk
Priority: optional
Section: non-free/devel
Filename: pool/contrib/o/oracle-j2sdk1.6/oracle-j2sdk1.6_1.6.0+update31_amd64.deb
Size: 96896162
SHA256: e3af578020ca3d595fbf1da7f006dde783fa10ace7e147ea135e5d09a8ad32b9
SHA1: 4b4cd040b2b71f1b754180d89c8e69f5940d27a5
MD5sum: 183149f3ddc42fcc03e137bea41cf85e
Description: Java(TM) JDK, Standard Edition, Oracle(TM)
The Java(TM) 2 SDK is a development environment for building
applications, applets, and components that can be deployed on the
Java(TM) platform.
.
The Java(TM) 2 SDK software includes tools useful for developing and
testing programs written in the Java programming language and running
on the Java platform. These tools are designed to be used from the
command line. Except for appletviewer, these tools do not provide a
graphical user interface.
.
This package has been automatically created with java-package (0.50).

BEGIN apt-get -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confold -y install oracle-j2sdk1.6
Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
libstdc++5
Recommended packages:
libgtk1.2
The following NEW packages will be installed:
libstdc++5 oracle-j2sdk1.6
END (100)
remote package oracle-j2sdk1.6 could not be installed, giving up
waiting for rollback request

0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 97.2 MB of archives.
After this operation, 232 MB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
libstdc++5 oracle-j2sdk1.6
E: There are problems and -y was used without --force-yes

1 2 3 4 5 6 7 8

[#6 · Accepted solution]

Login to all your hosts and try these commands, then click retry on the installation.

apt-get update
sudo apt-get install -y --force-yes debian-keyring debian-archive-keyring apt-transport-https
apt-key update
apt-get update

I have seen the "WARNING: The following packages cannot be authenticated!" message on Debian before and this has worked for me. 

Tina

[#7]

Thanks this worked for me!

[#8]

Yeah!  Glad it worked!!

Tina

[#9]

Hi,

I am also trying to setup a 3 node cluster. However I am using Cloudera CentOS 6.7.

And I am using PATH A for the setup

When i try to ./cloudera-manager-installer.bin with or without local repository it always has the same error.

[root@LnxMasterNode01 cloudera-manager-installer]# cat 2.install-oracle-j2sdk1.7.log
Loaded plugins: fastestmirror, security
Setting up Install Process
Repository cloudera-manager is listed more than once in the configuration
Loading mirror speeds from cached hostfile
No package oracle-j2sdk1.7 available.
Error: Nothing to do

I have turned off my iptables. But I already have Java pre-installed on all 3 servers.

[root@LnxMasterNode01 ~]# java -version
java version "1.7.0_95"
OpenJDK Runtime Environment (rhel-2.6.4.0.el6_7-x86_64 u95-b00)
OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)

Could this be the reason? If yes, how do I skip JDK installation and start with the second step i.e. postgress installation.

PS : my local repo looks like this

[root@LnxMasterNode01 yum.repos.d]# cat cloudera-cdh5.repo
[cloudera-cdh5]
name=Cloudera's Distribution for Hadoop, Version 5
baseurl=https://archive.cloudera.com/cdh5/redhat/6/x86_64/cdh/5/
gpgkey = https://archive.cloudera.com/cdh5/redhat/6/x86_64/cdh/RPM-GPG-KEY-cloudera 
gpgcheck = 1

[root@LnxMasterNode01 yum.repos.d]# cat cloudera-manager.repo
[cloudera-manager]
# Packages for Cloudera Manager, Version 5, on RedHat or CentOS 6 x86_64
name=Cloudera Manager
baseurl=https://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5/
gpgkey =https://archive.cloudera.com/cm5/redhat/6/x86_64/cm/RPM-GPG-KEY-cloudera
gpgcheck = 1

[root@LnxMasterNode01 yum.repos.d]#

Please help, I am running out of time.

Thanks in Advance.

Shilpa

[#10]

I was able to do the installation successfully. the problem was my cloudera-manager.repo and cloudera-cdh5.repo had the same content. I edited it using the correct repo location. As i mentioned in the above comment(i edited it post the changes done in cloudera-manager.repo.

See above comment for correct repos.

Thanks,

Shilpa