The first thing you need to do is recall what database you were using.    How did you add Cloudera Manager back?  You may have accidentally installed the Embedded database (cloudera-manager-server-db-2).  I would run "rpm -qa |grep cloudera" to see.   Cloudera Manager reads the database connection information from /etc/cloudera-scm-server/db.properties.  So, if you know your database connection information, you should be able to find it there.   Please run ls -lrt /etc/cloudera-scm-server and provide the listing here so we can see if there were any saved db.properties files that may be there.   If so, one may contain your old settings.   If you find them or edit the db.properties, restart Cloudera Manager after verifying the db.properties file is correct.     ... View more

Jamie,   Two questions:   (1)   How did you remove Cloudera Manager?  (What commands, etc.)   (2)   How did you determine your database wiped?     ... View more

In Cloudera Manager 5.5 and higher, service passwords are stored in Cloudera Manager so that they are not exposed in the process directories.  As part of this, the passwords are stored in a jceks file in each process directory.  A password is then passed to the start scripts to decrypt the file containing the passwords.   When attempting to run the "hue" command from the command line, you will get the following:   File "/opt/cloudera/parcels/CDH-5.6.0-1.cdh5.6.0.p0.45/lib/hue/desktop/core/src/desktop/lib/conf.py", line 276, in _coerce_type return self.type(raw) File "/opt/cloudera/parcels/CDH-5.6.0-1.cdh5.6.0.p0.45/lib/hue/desktop/core/src/desktop/conf.py", line 66, in coerce_password_from_script raise subprocess.CalledProcessError(p.returncode, script) subprocess.CalledProcessError: Command '/var/run/cloudera-scm-agent/process/4295-hue-HUE_SERVER/altscript.sh sec-8-password' returned non-zero exit status 1   This is because "altscript.sh" was not passed the password from CM. To help allow you to be able to run commands from the commandline, I suggest trying:   # export HUE_CONF_DIR=/var/run/cloudera-scm-agent/process/`ls -lrt /var/run/cloudera-scm-agent/process/ | awk '{print $9}' |grep HUE_SERVER| tail -1`   # HUE_IGNORE_PASSWORD_SCRIPT_ERRORS=1 HUE_DATABASE_PASSWORD=password /opt/cloudera/parcels/CDH/lib/hue/build/env/bin/hue livy_server   Since the Spark Notebook is not supported in CDH yet, we cannot guarantee it will work as desired, but at the least, the steps I give should help you get around the exception that @vganji mentioned. ... View more

The certificate_unknown message is received as an alert from the caller initiating the TLS session.  Generally, that means that the client making a connection to the server did not trust the certificate.   To find out who is really not trusting the NameNode certificate, check anything that connects to the NameNode.  Mostly, it is the DataNodes who need to hearbeat in I think.  Check your DataNode logs to find out if you get exceptions regarding trust when they attempt to make a connection.  For Resource Manager, check the NodeMangers' logs too.   Once you have reviewed the logs, you will likely have a better idea of what is going on.   You mentioned that "/var/lib/hadoop-hdfs/certs" is your truststore.  If it is, it should contain the certificate for every host in your cluster.  Also, make sure you have configured a path to it in the Service Configuration in HDFS:   "Cluster-Wide Default TLS/SSL Client Truststore Location" ... View more

The agent starts the supervisor (if one is not already running) by using the /var/run/cloudera-scm-agent/supervisor/supervisor.conf configuration.   The same supervisord.conf username and password is used to authenticate.  If authentication to the supervisor is failing, that indicates there is a supervisor running that was launched using a different supervisord.conf.   Run:   ps aux |grep supervisor   See if there is an existing supervisor process... you will likely need to kill it and then start the agent to make sure the agent is using the right supervisord.conf.   Regards,   Ben ... View more

Understood.  That was just a guess on which alternative may be causing the problem.  I'm not sure how to get alternatives to list the "--display" style output when just listing.  We may need to do some scripting to iterate over each alternative and write out the --display details for each to see which has more than 4 columns.   Alternatively, the only option would be to make code changes.       ... View more

Hello,   The exception occurs when the agent is attempting to run the "alternatives" command to list out all the current alternatives.  The agent code parses the output and assigns it to variables.  The exception indicates that one of the rows returned by "alternatives" has more columns than expected.   We see this assignment:   path, _, _, priority_str = line.rstrip().split(" ")   We have found that the OpenJDK name may have a space in the name so it has an extra column. We don't have a fix now, but you could remove OpenJDK from alternatives if that is the one with the extra column.   I'll make sure we tighten up the code to prevent this sort of issue in the future.     ... View more

A web search for "appliance cloudera" does come back with a few other hits like Teradata and Dell.  Whether they have been certified with multihomed configurations is not information that is generally available     ... View more