Open Nithinraot opened 6 years ago
wget https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/cloudera-manager.repo change the CM version accordingly inside the file baseurl = https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.11.2/
yum list all | grep cloudera-manager yum install cloudera-manager-server
[root@ip-172-31-20-193 schema]# sudo /usr/share/cmf/schema/scm_prepare_database.sh mysql -h ip-172-31-25-114 scm scm Enter SCM password: JAVA_HOME=/usr/java/jdk1.8.0_121-cloudera Verifying that we can write to /etc/cloudera-scm-server Creating SCM configuration file in /etc/cloudera-scm-server Executing: /usr/java/jdk1.8.0_121-cloudera/bin/java -cp /usr/share/java/mysql-connector-java.jar:/usr/share/java/oracle-connector-java.jar:/usr/share/cmf/schema/../lib/* com.cloudera.enterprise.dbutil.DbCommandExecutor /etc/cloudera-scm-server/db.properties com.cloudera.cmf.db. [ main] DbCommandExecutor INFO Successfully connected to database. All done, your SCM database is configured correctly!
Create the Issue Exit-test: Install CM Assign yourself and label it started Install Cloudera Manager on the second node listed in 0_setup.md List the command and output for ls /etc/yum.repos.d in challenges/labs/1_cm.md Copy cloudera-manager.repo to challenges/labs/2_cloudera-manager.repo.md Connect Cloudera Manager Server to its database Use the scm_prepare_database.sh script to create the db.properties file List the full command and its output in 2_properties.md Add the db.properties file content to 2_properties.md Start the Cloudera Manager server In challenges/labs/2_cm_startup.md add: The first line of the server log The line(s) that contain the phrase "Started Jetty server" Push these changes to GitHub and label the Issue review Assign the issue to the instructor