@Guru
Prathap
You might be hitting the issue reporte din the following link:
Java/Python Updates and Ambari Agent TLS Settings : https://community.hortonworks.com/articles/188269/javapython-updates-and-ambari-agent-tls-settings.h...
Solution For CentOS 7, Debian 7, Ubuntu 14 & 16, or SLES 12 (Python 2.7)
To
solve this problem simply configure the Ambari Agent to use TLSv1.2
when communicating with the Ambari Server by editing each Ambari Agent’s
/etc/ambari-agent/conf/ambari-agent.ini file and adding the following
configuration property to the security section:
[security]
force_https_protocol=PROTOCOL_TLSv1_2
Once
this configuration change has been made, the Ambari Agent needs to be
restarted. After restarting you should no longer see the ERROR’s in the
Ambari Agent logs, and in the Ambari Server UI you’ll notice that all
Ambari Agents are once again heartbeating.
Solution for CentOS 6, or SLES 11 (Python 2.6)
In
this scenario the only way forward is to edit the java.security file in
the JDK being used by the Ambari Server and make the following changes:
- Locate the jdk.tls.disabledAlgorithms property and remove the 3DES_EDE_CBC reference
- Save the file, and restart the Ambari Server
If
there are any other questions, or special circumstances not coverd in
this post, please create a support ticket with Hortonworks Support.
Also please check the "java.security" file of your Ambari Server JRE to see if it has the "jdk.tls.disabledAlgorithms" set properly as mentioned in article: https://community.hortonworks.com/articles/211781/jdk-changes-causing-ambari-serveragent-registratio...
# grep 'disabledAlgorithms' $JAVA_HOME/jre/lib/security/java.security
.
NOTE: Please make sure that you are looking at the correct JAVA_HOME which is being used by ambari server. You can confirm this by looking at the properties file:
# grep 'java.home' /etc/ambari-server/conf/ambari.properties
.
