@rjotwani-211490215,   The error message regarding the supervisor_status file can be ignored.  We will fix the code that generates that error sometime in the future. The message that indicates the cause of the formatting failure is:   Running in non-interactive mode, and data appears to exist in Storage Directory /dfs/nn. Not formatting. It may be you have some old data in /dfs/nn.  If you are sure you do not need what is in /dfs/nn you can copy it to another location or delete it.  Just be sure you don't need/want whatever is there. ... View more

@TCloud, The exception is in the agent and indicates to us that the agent is not able to verify the certificate that was returned by Cloudera Manager during the TLS handshake. In order to know why, we should look at what host the agent tried to contact (server_host in config.ini) and what certificates were listed in the SAN of the server certificate. You can use the following command to see what certificate is returned: openssl s_client -connect $(grep "server_host" /etc/cloudera-scm-agent/config.ini | sed s/server_host=//):7182 </dev/null | openssl x509 -text -noout Then, check to make sure agent's truststore has the proper certificate that trusts the CM cert.  To test, you can use: openssl s_client -connect $(grep -v '^#' /etc/cloudera-scm-agent/config.ini | grep "server_host=" | sed s/server_host=//):7182 -CAfile $(grep -v '^#' /etc/cloudera-scm-agent/config.ini | grep "verify_cert_file=" |sed s/verify_cert_file=//) -verify_hostname $(grep -v '^#' /etc/cloudera-scm-agent/config.ini | grep "server_host=" | sed s/server_host=//)</dev/null   The above is probably not that elegant, but you should be able to run it as it is.  It will grab your hostname and trust store file from the host's config.ini and then connect to your CM host to do a TLS handshake.  "-verify_hostname" will tell openssl to also do hostname validation to mimic what the agent does.   The result code of the above command should give us a better idea of why the handshake is failing.   ... View more

@wert_1311,   Cloudera and the agents will communicate to make sure that parcels are distributed and enabled on all hosts that are managed.  In this case, it sounds as if your attempts to copy information may have contributed to running out of space.  5GB isn't much space, though, so it could be you will need more space.   To allow the agent to correct the situation, you can do the following:   (1)   Stop the agent service cloudera-scm-agent stop   (2)   remove the contents of the parcels directory: /opt/cloudera/parcels/* (3)   Start the agent:   service cloudera-scm-agent start   (4)   Monitor the agent log to see if it starts downloading the files. ... View more

@Da,   CSD files used with CM 5 should be compatible with CM 6.  If you hit any problems that you think may be related to CM 6, please do let us know.     ... View more