Member since
01-26-2018
9
Posts
6
Kudos Received
2
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 6343 | 06-11-2020 04:38 AM | |
| 5756 | 05-26-2020 07:11 AM |
02-15-2021
12:08 PM
Good Day, Effective January 31, 2021, all Cloudera software requires a valid subscription and is only accessible from behind the paywall. This includes all legacy versions for Cloudera Distribution including Apache Hadoop (CDH), Hortonworks Data Platform(HDP), Data Flow (HDF/CDF),and Cloudera Data Science Workbench (CDSW). Information regarding paywall access will be available in technical documentation by software type and version. https://www.cloudera.com/downloads/paywall-expansion.html If you have a valid Cloudera Subscription, you can obtain your credentials for downloads following directions outlined here: https://docs.cloudera.com/cdp-private-cloud-base/latest/installation/topics/cdpdc-cm-download-information.html
... View more
06-11-2020
04:38 AM
2 Kudos
There is currently a bug. Please try the following: Click Parcel Repositories & Network Settings You should see a error that looks like: Remove that URL, and replace it with: https://archive.cloudera.com/cdh7/7.1.1.0/parcels/ This solution could be resolved or could change over time as newer versions of CM and Cloudera Runtime are released.
... View more
05-26-2020
07:11 AM
1 Kudo
Hello FrozenWave, Please give the following command a try: # rpm --import https://archive.cloudera.com/cm6/6.3.1/redhat7/yum/RPM-GPG-KEY-cloudera The reason you were having issues are that the repository URLs changed for version 6.3.3 and later as referenced here: https://docs.cloudera.com/documentation/enterprise/6/release-notes/topics/rg_cm_6_version_download.html The correct base URL for CM 6.3.1 is: https://archive.cloudera.com/cm6/6.3.1 Versus the URL you were trying to use, which requires authentication: https://archive.cloudera.com/p/cm6/6.3.1 I hope this helps!
... View more
03-18-2019
07:35 AM
If Director is creating the database via templates it will append a randomly generated string to the scm prefix so that multiple deployments can use the same database server without naming conflicts. The user you are using needs full administrative privileges to the entire database instance if going this route. If you are wanting to specify a pre-created database name and user, and only provide the user access to that one database, you will need to make sure to use something like the example in the attached link and deploy your environments via a conf file. https://www.cloudera.com/documentation/director/latest/topics/director_external_db_using.html cloudera-manager {
# ...
databases {
CLOUDERA_MANAGER {
name: scm1
type: mysql
host: 1.2.3.4
port: 3306
user: scmuser
password: scmpassword
}
# ...
}
} type - The type of database, “MYSQL” or “POSTGRESQL.”
hostname - The name of the server host.
port - The listening port of the server.
name - The name of the database on the server.
username - The name of the user account having full access to the database.
password - The password for the user account. Hope this helps!
... View more
03-15-2019
11:09 AM
It looks like your scm user doesn't have proper privileges to access the database server. This could be a problem with the grants in your mysql instance. [2019-03-14 23:36:19.504 +0500] INFO [io-thread-6] - - - - - ssh:10.142.0.54: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Access denied for user 'scm'@'%' to database 'scm_lsq85p3anqialkp12nogfhig3j'
[2019-03-14 23:36:19.504 +0500] INFO [io-thread-6] - - - - - ssh:10.142.0.54: at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)[:1.8.0_181] Cloudera Altus Director requires a username with full access to the database. https://www.cloudera.com/documentation/director/latest/topics/director_external_db_using.html
... View more