ERROR 2018-09-03 03:10:39,402 NetUtil.py:96 - EOF occurred in violation of protocol (_ssl.c:579)
ERROR 2018-09-03 03:10:39,403 NetUtil.py:97 - SSLError: Failed to connect. Please check openssl library versions.
Refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1022468 for more details.
WARNING 2018-09-03 03:10:39,403 NetUtil.py:124 - Server at https://localhost:8440 is not reachable, sleeping for 10 seconds...
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...
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:
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.
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:
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
Can you please share the latest Error which you got and also can you please share the output of thew following commands which we requested earlier?
Also please share the exact Operating System Version. And also after making the changes to the ambari-agent.ini script have you restarted the agent?
# grep 'java.home' /etc/ambari-server/conf/ambari.properties # grep 'disabledAlgorithms' $JAVA_HOME/jre/lib/security/java.security
As Upgrading to jdk1.8.0_171 version or later disables some of the TLSv1_1 TLSv1 protocols and algorithms which might be causing the issue so verifying the java version on ambari server host is also important. Please see: https://community.hortonworks.com/articles/211781/jdk-changes-causing-ambari-serveragent-registratio...
Was there is any JDK changes made on the server like upgrade of java or java security changes ?
Can you please paste the value of variable jdk.tls.disabledAlgorithms from file $JRE_HOME/lib/security/java.security
I believe changes in above parameter may have caused this issue
I am installing new ambari cluster. i am trying to add 3nodes, the 2 nodes was successful for one node i an getting this issue