Correct, a JDK 1.8 installation is required for C6 upgrade. Your options are: Upgrade to JDK 1.8 on the CM server host as shown in the upgrade guide, then upgrade JDK on the cluster nodes from the CDH 6 upgrade wizard Or upgrade the current cluster to JDK 1.8 usage first using these instructions, followed by the C6 upgrade ... View more

Thanks @anis447 this confirms this is the CDH package repository configured. This does not contain the JDK package as this is in the Cloudera Manager repository.   As first step please add the CM repository file as shown in documentation chapter. Then install Oracle JDK as shown here.   Please also confirm: What JDK version is installed right now, and why do you want to change JDK? Do you actually use (or intend to use) CDH RPM package based installation? Default and recommend is parcel based installation, please verify in the CM parcels page if CDH parcel is deployed from there. If so, the "cloudera-cdh5.repo" file can be removed. ... View more

Can you please list the repo file, to verify if the correct one is set?   # cat /etc/yum.repos.d/cloudera-cdh5.repo Based on the file name you may have configured the repository for CDH packages but not for CM packages, thus the JDK package will not be found. ... View more

@JoaquinS Your CM agent config file does not have TLS enabled, but the CM server configuration has.  I would suggest to disable the Use TLS Encryption for Agents, Use TLS Authentication of Agents to Server, Verify Agent Hostname Against Certificate settings and restart CM to proceed to make the installation work in a first step.   Once that is done, please follow the steps in this documentation chapter to enable TLS encryption for CM agent communication. ... View more

Sorry for the delay @yasmin  Not sure which files exactly you are referring to, but options are these are still valid data files from back then or they have been manually copied to there. You can easily verify with this procedure: Stop Service Monitor Make a backup of the whole data directory Delete the files in question Start Service Monitor Then monitor the Service Monitor logs after startup. If you see any errors or issues reported then those files are needed, then please revert the above procedure and restore the data directory from the backup. If there are no errors then you are fine with the deleted files. ... View more

Zipping files in the directory effectively breaks the index thus Host Monitor (same for Service Monitor) is expected to fail during startup. Regarding your question, yes please totally empty that directory while Service Monitor is shut down. The next startup will initialize the directory with the new index files, no issues expected. ... View more

Please attempt to start CM server again @sbommaraju Then look up /var/log/cloudera-scm-server/cloudera-scm-server.log as this should indicate potential reason for the startup failure. Also we suggest to start your own thread in the forums if you need further help with this startup error ... View more

Hi raphaelt,   not it's not possible to merge the two directories. You need to make a decision with which folder to proceed, thus where to have gaps in the charts in CM. ... View more