09-28-2017 05:45 AM - edited 09-28-2017 06:35 AM
the manager is looking for an EXTERNEL DB, but the SetUp was INTERNAL.
No I do not know the settings for:
Sep 28 14:44:03 SRV cloudera-scm-server-db: CM is using external DB. Failed to start embedded DB service, giving up
Sep 28 14:44:03 SRV su: pam_unix(su:session): session closed for user cloudera-scm
Sep 28 14:44:03 SRV systemd: cloudera-scm-server-db.service: Control process exited, code=exited status=1
Sep 28 14:44:03 SRV systemd: Failed to start LSB: Cloudera SCM Server's Embedded DB.
-- Subject: Unit cloudera-scm-server-db.service has failed
Can anyone help?
--- 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?
09-28-2017 09:22 AM
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:
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.