Hello @xiaocao  Sorry, there was a typo Please run the below command # telnet  <CM_SERVER_IP> 7182 # telnet <CM_SERVER_HOST> 7182 # systemctl status cloudera-scm-agent  ... View more

Hello @xiaocao  Can you check if all three PID's are cloudera process only # ps -ef | grep -i 15833 # ps -ef | grep -i 10429 # ps -ef | grep -i 15752 # netstat <CM_SERVER_IP> 7182 # netstat <CM_SERVER_HOST> 7182 ... View more

Hello, Thank you for your update Did hard restarting the agent helped?   # systemctl stop cloudera-scm-agent # systemctl stop cloudera-scm-supervisord # systemctl start cloudera-scm-agent   Also can you share the output of below command from the affected node # rpm -qa | grep -i cloudera # free -mh # df -hT # netstat -tulpn | grep -i 9000 # netstat -tulpn | grep -i 9001 ... View more

Hello @xiaocao  Can you try hard restarting the agent once # systemctl stop cloudera-scm-agent # systemctl stop cloudera-scm-supervisord # systemctl start cloudera-scm-agent Also it this a new installation or was it registered earlier with some other CM server?   ... View more

Hello @xiaocao  Thank you for reaching out to Cloudera Support Can you please check the /etc/cloudera-scm-agent/config.ini once on the affected node. Is server_host pointing to the CM server What is the CM and CDP version here? Check /var/log/messages from the affected node as well and see if find any errors regarding CM   ... View more

Hello @SIGOYI  I suspect some issues with config.ini Please move the current config.ini (/etc/cloudera-scm-agent/config.ini) to some other  location and copy /etc/cloudera-scm-agent/config.ini from CM server to this node and just replace server_host=192.168.88.54 (if this is localhost) Also run the below command # nslookup 192.168.88.54 (Get the hostname of CM server here) # nslookup <CM_SERVER_HOSTNAME> # telnet 192.168.88.54 7182 (just repeat once again) Then do a hard restart of the agent # systemctl stop cloudera-scm-agent # systemctl stop cloudera-scm-supervisord # systemctl start cloudera-scm-agent   ... View more

Hello, Thank you for your update So SSL Is not a problem here. Also as you mentioned that telnet is working which means connectivity is fine   Please check the below information now a.) Is port 9000 and other ports and enabled nothing else is running on them https://docs.cloudera.com/cdp-private-cloud-base/7.1.8/installation/topics/cdpdc-ports-used-by-cm.html b.) Can you compare the UUID of the host present in the file /var/lib/cloudera-scm-agent/uuid on the agent with the one that is visible on CM UI (ON CM UI >> Host >> all hosts >> Select this host and you will the UUID there) it should match with the one in uuid file on host if not then please collect the file using the below command # echo -n "UUID_copied from UI" > /var/lib/cloudera-scm-agent/uuid c.) Also check /var/log/messages from the node do you see any errors there d.) Check the /var/log/cloudera-scm-server/cloudera-scm-server.log and see if you observed any errors for this node over there e.) Also, if you have any other working node, I would suggest copying the /etc/cloudera-scm-agent/config.ini from working node to this node and then try restarting the agent Let me know if you have any further queries   ... View more

Hello @SIGOYI  Can you please confirm is 192.168.88.54 I think is getting an SSL from somewhere. Can you go to CM UI >> Administration >> Settings >> Click on Security and check if TLS is enforced on the agent from CM UI   ... View more

Hello @SIGOYI  Thank you for reaching out to the community I don't this is a Auto-TLS issue at this point. As use_tls=0 which means TLS is not enforced from the agent level Could you please check /var/log/cloudera-scm-agent/cloudera-scm-agent.log to check this further Also which TLS are you using on CM is it Auto-TLS or Manual TLS? If this is Auto-TLS, are the certificates signed by CM (Auto-TLS usecase 1) or your Custom CA (Auto-TLS use case)?   ... View more

Hello @shaihavivqlik  That's really strange. Usually, this error occurs when we cannot lookup  vault.localhost.localdomain Can you check your /etc/hosts as well? Also, try pinging your CM server as well  Something is for sure wrong in the DNS records. I don't we can check any logs as this is failing at the pre-reqs itself ... View more