ERROR Installing Agent

[#1]

Hi everyone

When installing cloudera-scm-agent, the installation failed due to heartbeat check failure. However, the backend logs show no errors and even output INFO-level logs indicating successful heartbeat detection. What could be the root cause?

agent.loginstalling logserver.log

[#2]

Hi, 

I'm used three virtual machines installed cloudera server and cloudera agent. Server installed in the first machine and agent in all the three machines. 

[#3]

Hi,

Below is the results

[#4]

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 

•  

[#5]

Hi,

I'm replace the IP address with hostname. And restart the cloudera-scm-agent. But it's  not helped

The TLS1_1 and TLS1_2 are all enabled.

I'm setted "Automatic configuration of TLS for services = No automatic configuration of TLS for services". And setted "use_tls=0" in /etc/cloudera-scm-agent/config.ini

[#6]

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

[#7]

Hi,

Thanks for your reply

 The TLS option is always 'no automatic configuration of TLS for services' 

I think I need to try reconfigure my environment and install cloudera again. Because my agent log show heartbeat is successed. And according to the server logs, the heartbeat signals from the agent were successfully received. I've double-checked that the rackIDs match between both logs. But here's the weird part – the WEBUI still throws a 'heartbeat missing' error. This is really puzzling!

[#8 · Accepted solution]

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

[#9]

Hi

Thanks for the tips!  I will use TLS Encryption for agents. Then try again