Member since
04-12-2016
124
Posts
20
Kudos Received
17
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2107 | 11-26-2018 06:59 AM | |
16340 | 06-18-2018 08:29 AM | |
5786 | 03-12-2018 11:46 AM | |
2607 | 01-29-2018 12:59 PM | |
5106 | 10-10-2017 11:12 AM |
02-07-2017
06:23 AM
Looks like you will need to manually install the required software: Requires: fuse-libs Requires: openssl-devel Requires: httpd Requires: fuse Requires: MySQL-python Requires: mod_ssl on all your hosts, then reinstall the Cloudera manager agents.
... View more
01-25-2017
09:01 AM
SLES12 SP2 does not install CM5.9.0. My installation failed also. I can't find any documentation that says it is a supported platform for CM5.9.0. Sorry
... View more
01-25-2017
08:32 AM
I don't see the CM Version in your reply, I assume it says: Version: Cloudera Enterprise Data Hub Edition Trial 5.9.1 (#8 I will try to install this on SLES12 SP2 now. Will let you know if it works for me. Tina
... View more
01-25-2017
07:50 AM
Sounds like your Cloudera Manager Server is not running 5.9.1, but you are trying to install the 5.9.1 agent. What version of the CM Server do you have running? Lookin the CM UI drop down SUPPORT > ABOUT top rigth hand corner on CM UI home page The server and agent versions have to match. Tina
... View more
11-15-2016
08:02 AM
No, you do not have to re-install CDH. Here is a document that shows you how to move Cloudera Manager to a new host and steps to take so your CDH hosts will see it. http://www.cloudera.com/documentation/enterprise/latest/topics/cm_ag_restore_server.html Moving the Cloudera Manager Server to a New Host You can move the Cloudera Manager Server if either the Cloudera Manager database server or a current backup of the Cloudera Manager database is available. To move the Cloudera Manager Server: Identify a new host on which to install Cloudera Manager. Install Cloudera Manager on a new host, using the method described under Install the Cloudera Manager Server Packages. Important: The Cloudera Manager version on the destination host must match the version on the source host. Do not install the other components, such as CDH and databases. Copy the entire content of /var/lib/cloudera-scm-server/ on the old host to that same path on the new host. Ensure you preserve permissions and all file content. If the database server is not available: Install the database packages on the host that will host the restored database. This could be the same host on which you have just installed Cloudera Manager or it could be a different host. If you used the embedded PostgreSQL database, install the PostgreSQL package as described in Embedded PostgreSQL Database. If you used an external MySQL, PostgreSQL, or Oracle database, reinstall following the instructions in Cloudera Manager and Managed Service Datastores. Restore the backed up databases to the new database installation. Update /etc/cloudera-scm-server/db.properties with the database name, database instance name, username, and password. Do the following on all cluster hosts: In /etc/cloudera-scm-agent/config.ini, update the server_host property to the new hostname. If you are replacing the Cloudera Manager database with a new database, and you are not using a backup of the original Cloudera Manager database, delete the /var/lib/cloudera-scm-agent/cm_guid file. Restart the agent using the following command: $ sudo service cloudera-scm-agent restart Start the Cloudera Manager Server. Cloudera Manager should resume functioning as it did before the failure. Because you restored the database from the backup, the server should accept the running state of the Agents, meaning it will not terminate any running processes. The process is similar with secure clusters, though files in /etc/cloudera-scm-server must be restored in addition to the database. See Cloudera Security.
... View more
11-14-2016
06:11 AM
For #1, do you mean upgrade Cloudera Manager? I am not sure what you mean by re-install? If you upgrade Cloudera Manager you do not have to upgrade CDH to the same version. Tina
... View more
11-07-2016
06:42 AM
1 Kudo
https://community.cloudera.com/t5/Cloudera-Manager-Installation/cloudera-scm-server-is-dead-and-pid-file-exists/td-p/22701 is the same problem. It says: Since there is a .pid file, remove it first. Check the following and delete if it exists: /var/run/cloudera-scm-server.pid Try this.
... View more
10-25-2016
09:35 AM
Many of the health issues could be related to free space issues. If you fix the free space issues (You can just change the threshold that triggers the free space issue or surpress the issues) and wait a few minutes, most of you other issues may go away.
... View more
10-13-2016
08:11 AM
I found a jira that was entered for CM5.7.0 release. This was the reason given for the error for that installation: We have a mismatch between null and undefined. One of the steps detected having multiple versions of CDH and returned null. Later on we only check against undefined. This problem has been fixed in CM5.7.0. If you can upgrade CM to 5.7.0 you should not see it. A note also said that logging out of CM and back in seemed to fix the problem, that could be how the other older entries got fixed last year. Tina
... View more
10-07-2016
06:37 AM
Yeah! Glad it worked!! Tina
... View more
- « Previous
- Next »