This is the documentation for Cloudera Manager 5.0.x. Documentation for other versions is available at Cloudera Documentation.

Embedded PostgreSQL Database

Continue reading:

Installing and Starting the Embedded PostgreSQL Database

If you are using Installation Path B - Manual Installation Using Cloudera Manager Packages for a demonstration or proof of concept deployment, and you want to use an embedded PostgreSQL database, use this procedure to install and start the database:
  1. Install the embedded PostgreSQL database packages:
    • Red Hat-compatible, if you have a yum repo configured:
      $ sudo yum install cloudera-manager-server-db-2
    • Red Hat-compatible, if you're transferring RPMs manually:
      $ sudo yum --nogpgcheck localinstall cloudera-manager-server-db-2.noarch.rpm
    • SLES:
      $ sudo zypper install cloudera-manager-server-db-2
    • Debian/Ubuntu
      $ sudo apt-get install cloudera-manager-server-db-2
  2. Start the PostgreSQL database:
    $ sudo service cloudera-scm-server-db start

Stopping the Embedded PostgreSQL Database

  1. Stop the services that have a dependency on the Hive Metastore (Hue, Impala, and Hive). You will not be able to stop the Cloudera Manager Server database while these services are running. Stop services that depend on the Hive Metastore in the following order:
    • Stop the Hue and Impala services.
    • Stop the Hive service.
  2. Stop Management Services.
  3. Stop Cloudera Manager Server.
    sudo service cloudera-scm-server stop
  4. Stop Cloudera Manager Server Database.
    sudo service cloudera-scm-server-db stop

Backing up Embedded PostgreSQL Databases

After stopping the database, back up the /var/lib/cloudera-scm-server-db directory.

Changing Embedded PostgreSQL Database Passwords

The embedded PostgreSQL database has predefined user accounts and passwords. To change passwords associated with the embedded PostgreSQL database accounts retrieve the user name or password, as well as other database information as follows:

  • The Cloudera Manager service connects to the database using the scm account. Information about this account is stored in the db.properties file.
  • The root account for the database is the cloudera-scm account. Information about this account is stored in the generated_password.txt file.
To find information about the PostgreSQL database user account that the SCM service uses, read the /etc/cloudera-scm-server/db.properties file:
# cat /etc/cloudera-scm-server/db.properties

Auto-generated by scm_prepare_database.sh
#
Sat Oct 1 12:19:15 PDT 201
#
com.cloudera.cmf.db.type=postgresql
com.cloudera.cmf.db.host=localhost:7432
com.cloudera.cmf.db.name=scm
com.cloudera.cmf.db.user=scm
com.cloudera.cmf.db.password=TXqEESuhj5
To find information about the root account for the database, read the /var/lib/cloudera-scm-server-db/data/generated_password.txt file:
# cat /var/lib/cloudera-scm-server-db/data/generated_password.txt

MnPwGeWaip

The password above was generated by /usr/share/cmf/bin/initialize_embedded_db.sh (part of the cloudera-scm-server-db package)
and is the password for the user 'cloudera-scm' for the database in the current directory.

Generated at Fri Jun 29 16:25:43 PDT 2012.

Once you have gathered passwords, you can change the passwords for users, if desired.

Page generated September 3, 2015.