Cloudera Enterprise 5.15.x | Other versions

Reverting a Failed Cloudera Manager Upgrade

This topic describes how to reinstall the same version of Cloudera Manager you were using previously, so that the version of your Cloudera Manager Agents match the server. The steps below assume that the Cloudera Manager Server is already stopped (as it failed to start after the attempted upgrade).

Loading Filters ...

Important: The following instructions assume that a Cloudera Manager upgrade failed, and that the upgraded server never started, so that the remaining steps of the upgrade process were not performed. The steps below are not sufficient to revert from a running Cloudera Manager 5 deployment.

Establish Access to the Software

Cloudera Manager needs access to a package repository that contains the updated software packages.

If the Cloudera Manager server host has internet access, you can use the publicly available repositories from https://archive.cloudera.com. Fill in the form at the top of this page to generate the repository file for your system and the version of Cloudera Manager you want to upgrade to. The file created allows you to upgrade to the latest maintenance version for that minor version.

If the Cloudera Manager server host does not have internet access, configure a local package repository hosted on your network, and enter the repository URL below to generate the repository file. For example: http://MyHostname:port/cm

Package Repository URL:

Redhat / CentOS

Create a file named cloudera_manager.repo with the following content:

[cloudera-manager]
# Packages for Cloudera Manager
name=Cloudera Manager
baseurl=https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.15
gpgkey=https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/RPM-GPG-KEY-cloudera
gpgcheck=1

SLES

Create a file named cloudera_manager.repo with the following content:

[cloudera-manager]
# Packages for Cloudera Manager
name=Cloudera Manager
baseurl=https://archive.cloudera.com/cm5/sles/12/x86_64/cm/5.15
gpgkey=https://archive.cloudera.com/cm5/sles/12/x86_64/cm/RPM-GPG-KEY-cloudera
gpgcheck=1

Debian / Ubuntu

Create a file named cloudera_manager.list with the following content:

# Packages for Cloudera Manager
deb https://archive.cloudera.com/cm5/debian/jessie/amd64/cm/ jessie-cm5.15 contrib
deb-src https://archive.cloudera.com/cm5/debian/jessie/amd64/cm/ jessie-cm5.15 contrib

The repository file, as created, specifies an upgrade to the most recent maintenance release of the specified minor release. If you would like to upgrade to an specific maintenance version, for example 5.15.1, replace 5.15 with 5.15.1 in the generated repository file shown above.

Backup the existing repository directory.

Redhat / CentOS

sudo cp -rf /etc/yum.repos.d $HOME/yum.repos.d-`date +%F`

SLES

sudo cp -rf /etc/zypp/repos.d $HOME/repos.d-`date +%F`

Debian / Ubuntu

sudo cp -rf /etc/apt/sources.list.d $HOME/sources.list.d-`date +%F`

Remove any older files in the existing repository directory:

Redhat / CentOS

sudo rm /etc/yum.repos.d/cloudera*manager.repo*

SLES

sudo rm /etc/zypp/repos.d/cloudera*manager.repo*

Debian / Ubuntu

sudo rm /etc/apt/sources.list.d/cloudera*.list*

Copy the repository file created above to the repository directory:

Redhat / CentOS

sudo cp cloudera_manager.repo /etc/yum.repos.d/

SLES

sudo cp cloudera_manager.repo /etc/zypp/repos.d/

Debian / Ubuntu

sudo cp cloudera_manager.list /etc/apt/sources.list.d/

Downgrade the Cloudera Manager Server

Stop the Cloudera Manager Embedded Database if you are using the embedded PostgreSQL database.
Redhat 7, SLES 12, Debian 8, Ubuntu 16.04
```
sudo systemctl stop cloudera-scm-server-db
```
Redhat 5 or 6, SLES 11, Debian 6 or 7, Ubuntu 12.04, 14.04
```
sudo service cloudera-scm-server-db stop
```
If you are not using the embedded PostgreSQL database and you attempt to stop it, you may see a message indicating that the service cannot be found. If you see a message that the shutdown failed, the embedded database is still running, probably because services are connected to the Hive metastore. If the database shutdown fails due to connected services, issue the following command:
RHEL-compatible 7 and higher, Ubuntu 16.04
```
sudo service cloudera-scm-server-db next_stop_fast
```
```
sudo service cloudera-scm-server-db stop
```
All other Linux distributions
```
sudo service cloudera-scm-server-db fast_stop
```
Stop the Cloudera Manager Agent.
Redhat 7, SLES 12, Debian 8, Ubuntu 16.04
```
sudo systemctl stop cloudera-scm-agent
```
Redhat 5 or 6, SLES 11, Debian 6 or 7, Ubuntu 12.04, 14.04
```
sudo service cloudera-scm-agent stop
```
Downgrade the packages. Note: Only add cloudera-manager-server-db-2 if you are using the embedded PostgreSQL database.
Redhat / CentOS
```
sudo yum clean all
sudo yum repolist
```
```
sudo yum downgrade cloudera-manager*
```
SLES
```
sudo zypper clean --all
```
```
sudo zypper dup -r baseurl
```
Debian / Ubuntu

There is no action that downgrades to the version currently in the repository. Read DowngradeHowto, download the script described therein, run it, and then run apt-get install for the name=version pairs that it provides for Cloudera Manager.

Verify that you have the correct packages installed.

rpm -qa 'cloudera-manager-*'

cloudera-manager-server-5.15.0-..cm...
cloudera-manager-agent-5.15.0-..cm...
cloudera-manager-daemons-5.15.0-..cm...
cloudera-manager-server-db-2-5.15.0-..cm...

dpkg-query -l 'cloudera-manager-*'

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                   Version                Description
+++-======================-======================-============================================================
ii  cloudera-manager-agent 5.15.0-0.cm...~sq The Cloudera Manager Agent
ii  cloudera-manager-daemo 5.15.0-0.cm...~sq Provides daemons for monitoring Hadoop and related tools.
ii  cloudera-manager-serve 5.15.0-0.cm...~sq The Cloudera Manager Server

If you are using the embedded PostgreSQL database, start the database :
Redhat 7, SLES 12, Debian 8, Ubuntu 16.04
```
sudo systemctl start cloudera-scm-server-db
```
Redhat 5 or 6, SLES 11, Debian 6 or 7, Ubuntu 12.04, 14.04
```
sudo service cloudera-scm-server-db start
```
Start the Cloudera Manager Agent.
Redhat 7, SLES 12, Debian 8, Ubuntu 16.04
```
sudo systemctl start cloudera-scm-agent
```
You should see no response if there are no errors starting the agent.
Redhat 5 or 6, SLES 11, Debian 6 or 7, Ubuntu 12.04, 14.04
```
sudo service cloudera-scm-agent start
```
You should see the following:
```
Starting cloudera-scm-agent: [ OK ]
```
Start the Cloudera Manager Server.
Redhat 7, SLES 12, Debian 8, Ubuntu 16.04
```
sudo systemctl start cloudera-scm-server
```
You should see no response if there are no errors starting the Cloudera Manager server.
Redhat 5 or 6, SLES 11, Debian 6 or 7, Ubuntu 12.04, 14.04
```
sudo service cloudera-scm-server start
```
You should see the following:
```
Starting cloudera-scm-server: [ OK ]
```

Note: If you have problems starting the server, such as database permissions problems, you can use the server's log to troubleshoot the problem.

vim /var/log/cloudera-scm-server/cloudera-scm-server.log

Page generated May 18, 2018.