About upadhyayk04

upadhyayk04 · ‎03-06-2025

Hello @SIGOYI Just want to follow up Are you still facing issue if yes then lets capture the TCP dump on port 7182 of CM server and see if the request is reaching out to CM or not form the affected node

upadhyayk04 · ‎03-06-2025

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

upadhyayk04 · ‎03-05-2025

Hello @xiaocao Thank you for your update I was actually concerned with the below settings Use TLS Encryption for Agents Use TLS Authentication of Agents to Server Anyways if you are observing heartbeat success in the agent and server_host is correct set to CM server in /etc/cloudera-scm-agent/config.ini then two things we will need to check a.) CM Server logs (/var/log/cloudera-scm-server/cloudera-scm-server.log) on CM server host b.) capture network packet dump on CM side on port 7182 and analyze the packets on port 7182 whether client request is reaching or not

upadhyayk04 · ‎03-05-2025

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

upadhyayk04 · ‎03-05-2025

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

upadhyayk04 · ‎03-05-2025

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

upadhyayk04 · ‎03-05-2025

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

upadhyayk04 · ‎03-05-2025

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

upadhyayk04 · ‎03-05-2025

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?

upadhyayk04 · ‎03-05-2025

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

Online	Online
Last Visited	‎12-16-2025 10:28 PM

Member Since	‎02-07-2022 04:14 AM
Last Visited	‎12-16-2025 10:28 PM
Posts	264
Kudos received	61

Cloudera Community

Re: Ranger Auditor Role

Re: Apache Ozone -1.4. Upgrading parcel version t...

Re: Cannot erase old /opt/cloudera/parcels

Re: swap warning

Re: Getting access denied in MariaDB for Reports M...

Re: cdh6.3.2 15528 MainThread agent ERROR Heartbea...

Re: Error while installing Data Services

Re: ERROR Installing Agent

Re: ERROR Installing Agent

Re: ERROR Installing Agent

Re: ERROR Installing Agent

Re: ERROR Installing Agent

Re: ERROR Installing Agent

Re: ERROR Installing Agent

Re: ERROR Installing Agent