Hello, Thank you for your update Can you please confirm if you are able to ping localhost  # nslookup localhost How many nameservers are present in /etc/resolv.conf ... View more

Hello @xiaocao  You will need to uncheck the TLS options for the agent under the below path and then restart the CM server and agent CM UI >> Administation >> Settings >> Click on Security  # systemctl restart cloudera-scm-server on agent # systemctl restart cloudera-scm-agent   ... View more

Hello @xiaocao  Thank you for your update Could you please confirm if TLS is enabled? If yes then which TLS Also I could see that nslookup is not working using IP address so can you please confirm the value of server_host in /etc/cloudera-scm-agent/config.ini if this a IP address then please replace it with hostname   If possible, please upload the /etc/cloudera-scm-agent/config.ini Also from CM UI >> Administation >> Settings >> Click on Security        ... View more

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