This was reported as a bug, and has already been fixed in CM 6.3.0, 6.2.1 as part of OPSAPS-49111 ... View more

@ADingmando you have a use case, or you have any particular issue that you'd like assistance with?   The ODBC Drivers are built for CDH and HDP release. I believe there should be a release notes if you unpack the contents and compare the fixes each ODBC driver contains. ... View more

> few days ago my CM started successfully. But, after restarted my server, it raised that error when I started. Unfortunately without the logs, or stack trace I won't be able to assess what caused the error.   Back to the intermixed "scm" and "metastore" database issue;   > "Now I tried to drop all the databases in mysql and create again, then run the following command respectively :" I think there may have been some misunderstanding, about the intention of the script "/opt/cloudera/cm/schema/scm_prepare_database.sh". The script as the documenatation state, is to create and configure a database for iteself [Cloudera Manager Server] [0]   As seen in your comment, you've used for various services (amon, rman, ... metastore, ... etc)   Please do check in your RDBMS (MySQL), and confirm which database name CM should be connecting to. eg: mysql> show databases; and for each database confirm which one has the correct schema with the "CM_VERSION" table in. mysql> show tables;   or something like this; SELECT table_name, table_schema AS dbname FROM INFORMATION_SCHEMA.TABLES WHERE table_name='CM_VERSION' Note this is just a suggestion, to find the correct database where CM server can connect to.     [0] https://www.cloudera.com/documentation/enterprise/latest/topics/prepare_cm_database.html#cmig_topic_5_2     ... View more

The location of "scm_prepare_database.sh" will change in CM 6.x, I will check with our documentation team as this may be a doc issue.    For CM 5.x please use the default location, such as "/usr/share/cmf/schema/scm_prepare_database.sh"   You can check this by listing the rpm contents.   # rpm -qlp http://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.15/RPMS/x86_64/cloudera-manager-daemons-5.15.0-1.cm5150.p0.62.el7.x86_64.rpm | grep scm_prepare_database.sh /usr/share/cmf/schema/scm_prepare_database.sh Let me know if this helps ... View more

Hi Sandy,       + ktutil + for ENC in '"${ENC_ARR[@]}"' + echo 'addent -password -p cloudera-scm/REDACTED@PRICLUSTER.COM -k 1 -e aes256-cts:normal' + '[' 0 -eq 1 ']' + echo REDACTED + for ENC in '"${ENC_ARR[@]}"' + echo 'addent -password -p cloudera-scm/REDACTED@PRICLUSTER.COM -k 1 -e aes128-cts:normal' + '[' 0 -eq 1 ']' + echo REDACTED + for ENC in '"${ENC_ARR[@]}"' + echo 'addent -password -p cloudera-scm/REDACTED@PRICLUSTER.COM -k 1 -e des3-hmac-sha1:normal' + '[' 0 -eq 1 ']' + echo REDACTED + for ENC in '"${ENC_ARR[@]}"' + echo 'addent -password -p cloudera-scm/REDACTED@PRICLUSTER.COM -k 1 -e des-hmac-sha1:normal' + '[' 0 -eq 1 ']' + echo REDACTED + for ENC in '"${ENC_ARR[@]}"' + echo 'addent -password -p cloudera-scm/REDACTED@PRICLUSTER.COM -k 1 -e des-cbc-crc:normal' + '[' 0 -eq 1 ']' + echo REDACTED + echo 'wkt /var/run/cloudera-scm-server/cmf8091152271730902012.keytab' addent: Bad encryption type while adding new entry ktutil: Unknown request "REDACTED". Type "?" for a request list. addent: Bad encryption type while adding new entry ktutil: Unknown request "REDACTED". Type "?" for a request list. addent: Bad encryption type while adding new entry ktutil: Unknown request "REDACTED". Type "?" for a request list. addent: Bad encryption type while adding new entry ktutil: Unknown request "REDACTED". Type "?" for a request list. addent: Bad encryption type while adding new entry ktutil: Unknown request "REDACTED". Type "?" for a request list. + chmod 600 /var/run/cloudera-scm-server/cmf8091152271730902012.keytab chmod: cannot access `/var/run/cloudera-scm-server/cmf8091152271730902012.keytab': No such file or directory   Base on the above information, I've noticed that you have set the encryption in  CM UI> Administration> Setting> Kerberos> "Kerberos Encryption Types" as  - aes256-cts:normal - aes128-cts:normal - des3-hmac-sha1:normal - des-hmac-sha1:normal - des-cbc-crc:normal   The error I see is that while ktutil executed the command addent it failed with "Bad encryption type while adding new entry"   Therefore, ktutil failed to set -e encryption_type for all 5 encryption types you've specified, so there was nothing to be written into a keytab (wkt keytab) see: 'wkt /var/run/cloudera-scm-server/cmf8091152271730902012.keytab'       The encryption type combination you've specified is valid for kadmin/kadmin.local tool where the -e parameter can be specified as encryption:salt, but it is not valid for ktutil -e encryption_type   Since CM script is using ktutil you may need to remove the salt suffixed ':normal'. The salt :normal is default for Kerberos Version 5, you only need to set the encryption type [0] in  CM UI> Administration> Setting> Kerberos> "Kerberos Encryption Types"   Encryption Type - aes256-cts - aes128-cts - des3-hmac-sha1 - des-hmac-sha1 - des-cbc-crc   Let me know if this helps,   Michalis   [0] https://web.mit.edu/kerberos/krb5-latest/doc/admin/conf_files/kdc_conf.html#encryption-types Note: A feature request OPSAPS-29768 is in progress to not allow manual entry in "Kerberos Encryption Types" ... View more