Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

No access to the cluster after rebooing the management Serverr

No access to the cluster after rebooing the management Serverr

New Contributor

Hi,

 

the manager is looking for an EXTERNEL DB, but the SetUp was INTERNAL.

No I do not know the settings for:

 

com.cloudera.cmf.db.type=postgresql
com.cloudera.cmf.db.host=localhost
com.cloudera.cmf.db.name=?
com.cloudera.cmf.db.user=?
com.cloudera.cmf.db.setupType=INTERNAL (?)
com.cloudera.cmf.db.password=****

 

Sep 28 14:44:03 SRV cloudera-scm-server-db[23593]: CM is using external DB. Failed to start embedded DB service, giving up
Sep 28 14:44:03 SRV su[23612]: pam_unix(su:session): session closed for user cloudera-scm
Sep 28 14:44:03 SRV systemd[1]: cloudera-scm-server-db.service: Control process exited, code=exited status=1
Sep 28 14:44:03 SRV systemd[1]: Failed to start LSB: Cloudera SCM Server's Embedded DB.
-- Subject: Unit cloudera-scm-server-db.service has failed

 

Can anyone help?

 

Best

Andy

 

--- upgrade ---

 

the setup change from INT to EXT databse (but why?)

 

but there was a file db.properties.~1~ with the values I needed.

 

Is there a good article how to setup a external postgres DB?

1 REPLY 1

Re: No access to the cluster after rebooing the management Serverr

Super Guru

Hello @Vogone,

 

You have encountered a safeguard which should prevent the reconfiguring of your Cloudera Manager database from its previous setting due to having the embedded database package (cloudera-manager-server-db-2)

 

First, check to see if your current db.properties is correct:

cat /etc/cloudera-scm-server/db.properties

 

If it is not correct, then check for other db.properties.xxxx files in /etc/cloudera-scm-server/ directory to see if any are correct.

copy the correct one to db.properties if the current one is not correct.

 

If you have configured Cloudera Manager to use a non-embedded database (as it seems you have not), then remove the "cloudera-manager-server-db-2" package from your Cloudera Manager host.  When you reboot, it is configured to start.  When cloudera-manager-server-db-2 package starts (cloudera-scm-server-db) it will attempt to configure your db.properties to connect to an "embedded" postgres db.

 

Once you have the correct db.properties file configured and the cloudera-manager-server-db-2 package is removed, start Cloudera Manager.