Hi Dennistanpunya,   The pictures do show some useful information. The agent host is unable to heartbeat in, and CM server setup/installation doesn't appear to have fully completed the Cloudera Manager setup or know about this node.   A step may have been missed while setting up the Cloudera Manager CA. There should be more details in the /var/log/cloudera-scm-agent/certmanager.log if the certmanager run had any issues.   Was Cloudera Manager server started? its required to login to the Cloudera Manager and add the new nodes to Cloudera manager Hosts in the UI (or via API). During the agent installation Cloudera Manager Server will ssh login as root to install the agent rpm's and distribute the proper TLS keys and configurations for each node automatically.   We've also included some links below, specifically to the section on configuring TLS encryption for Cloudera Manager and CDH using Auto-tls. From your description, the section "Enabling Auto-TLS to automatically create certificates" should help.   https://www.cloudera.com/documentation/enterprise/6/6.0/topics/install_cm_server.html https://www.cloudera.com/documentation/enterprise/latest/topics/auto_tls.html#auto_tls_cm_ca     ... View more

Hi   noticing this error  "Caused by: java.io.EOFException: read past EOF: MMapIndexInput(path="/var/lib/you_metadata_path")"   When errors like this appear in the logs its usually a sign that the internal solr core index has become corrupted somehow from missing files, and the index will need to be regenerated again over time as fresh metadata comes in.   Stopping the Navigator Metadat Server, Clearing the metadata directory and starting a fresh index like this is the best option if this occurs.. It seems to occur most commonly from disks filling up, or a hard server crash of some sort.   -T   ... View more