FAQ
I ran into an issue when trying to upgrade to CM5 beta from CM4 on an AWS
instance.

This was after server upgrade completed and I was trying to upgrade hosts.
CM was trying to connect to the public name of the local host instead of
the internal name even though I provided it the internal name to upgrade
hosts.

I am speculating that the following issue may have been to blame in that I
had ran into this on the initial CM4 installation:

http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM5/latest/Cloudera-Manager-Release-Notes/cm5rn_known_issues.html

(See: — Installing on AWS, you must use private EC2 hostnames)
The only way I was able to get past the issue was by completely removing CM
then adding it back - including the following commands to purge:

apt-get purge cloudera-manager-server-db

apt-get purge cloudera-manager-server

apt-get purge cloudera-manager-agent
Fortunately HDFS was not harmed during this process in my case.
- Richard

To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedNov 2, '13 at 5:43a
activeNov 2, '13 at 5:43a
posts1
users1
websitecloudera.com
irc#hadoop

1 user in discussion

Richard Williamson: 1 post

People

Translate

site design / logo © 2022 Grokbase