Hello,   If you are getting the same errors as indicated in the original post that each management service cannot fetch the descriptor, that indicates a problem for the management services contacting Cloudera Manager.  In order to know what hosts, services, and roles participate in the cluster (among other things), the management services must be able to retrieve the a descriptor for the cluster from CM upon startup.  If it cannot be retreived, then the management service will fail to start all the way.   The original post shows that the root cause of this is that no connection can be made.  If SSL is not involved, then typically there is a firewall or some other configuration issue that is preventing the management services from resolving/connecting.  If you have exactly the same stack traces, I would try shutting off any firewalls on the hosts where the management services run and where Cloudere Manager runs.  Try using telnet or ncat to ensure that you can make a connection from the management service host to the CM host.   If that doesn't help, you might post the exceptions you are seeing as there may be something different about the cause in your case.   -Ben ... View more

Hi Kevin,   CM 5.4.1 is the latest version at this time so that's why you can't find it.   CDH 5.4.2 is not too new for CM 5.4.1, so you should be able to proceed.   If there is a problem, a screen shot should help us figure out what to do.   - Ben ... View more

Hello,   In order to debug this further we'll need to know what is calling into the version string check.  The message you see, "Cannot have empty version string segment" is coming from a part of code that is called from various classes.   Please look at your /var/log/cloudera-scm-server/cloudera-scm-server.log and see if there is a "Cannot have empty version string segment" message and a stack trace associated with it.  If so, please include the full stack trace and error.   Based on the code, I am not sure if we will actually get a stack, but I'm hoping!   - Ben ... View more

Your error is slightly different and indicates another cause.     If you are are using single user mode, then see this:   http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/install_singleuser_reqts.html   Note the Configuration Steps Before Running the Installation Wizard section:   Even if you are not, I think this maybe relevant:     cloudera-scm ALL=(ALL) NOPASSWD: ALL   Setting NOPASSWD on the user (in the sudoers file) that you you specified in the installation wizard will likely resolve the issue you see.   - Ben ... View more

As dlo mentioned, you need to use "Create Database" from Cloudera Manager.  You can also create it from the command line if not using Cloudera Manager.  See the following for more information:   http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cm_mc_oozie_service.html#cmig_topic_14_unique_1   Ben ... View more

The extension does not matter, but the format does.  The file should be in "PEM" format.  It should contain these lines:   -----BEGIN CERTIFICATE----- -----END CERTIFICATE-----   -Ben ... View more

Please post the entire stack so that there is some context for the exception   Thanks. ... View more