Hello @Lavenda  Thank you for reaching out to community Can you please confirm what is the heap assigned to CM server? You can check the same in /etc/default/cloudera-scm-server Also, do you see JVM pauses in /var/log/cloudera-scm-server/cloudera-scm-server.log.   If you see JVM pauses in the above logs try increasing the heap for CM server and restart the cloudera-scm-server service (systemctl restart cloudera-scm-server)   # cat /var/log/cloudera-scm-server/cloudera-scm-server.log | grep -i "Detected pause in JVM"   ... View more

  @satz The image is the result of the last check step, which is to connect to localhost:7180 and add the cluster after installing the OS using the commands on the trial install page. In this situation, the status of the cluster shows that namenode is down. After that, no matter how many times you refresh the page or restart through the command in the OS, you will get the access denied (page cannot be opened) message when you connect to the CM. Also, I install it on one OS and proceed, but sometimes, during the process of adding a cluster, only the OS installed at the time of host inspection is installed in the cluster, and the rest of the OSs are removed. (Sometimes I can completely reinstall the OSs afterward, and sometimes I can't, but I don't know the difference. The log is so long that I want to upload the file, but there is no upload function. ... View more