[ 
https://issues.apache.org/jira/browse/AMBARI-23222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated AMBARI-23222:
------------------------------------
    Labels: pull-request-available  (was: )

> Ambari-agent fails to connect to server with two_way_auth enabled
> -----------------------------------------------------------------
>
>                 Key: AMBARI-23222
>                 URL: https://issues.apache.org/jira/browse/AMBARI-23222
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>         Attachments: AMBARI-23222.patch
>
>
>     ERROR 2018-03-13 17:15:04,264 security.py:122 - Could not connect to 
> wss://ctr-e138-1518143905142-94896-01-000002.hwx.site:8441/agent/stomp/v1
>     Traceback (most recent call last):
>       File "/usr/lib/ambari-agent/lib/ambari_agent/security.py", line 113, in 
> establish_connection
>         conn.start()
>       File "/usr/lib/ambari-agent/lib/ambari_stomp/connect.py", line 46, in 
> start
>         self.transport.start()
>       File "/usr/lib/ambari-agent/lib/ambari_stomp/transport.py", line 109, 
> in start
>         self.attempt_connection()
>       File "/usr/lib/ambari-agent/lib/ambari_stomp/adapter/websocket.py", 
> line 89, in attempt_connection
>         self.ws.connect()
>       File "/usr/lib/ambari-agent/lib/ambari_ws4py/client/__init__.py", line 
> 216, in connect
>         self.sock.connect(self.bind_addr)
>       File "/usr/lib64/python2.7/ssl.py", line 869, in connect
>         self._real_connect(addr, False)
>       File "/usr/lib64/python2.7/ssl.py", line 860, in _real_connect
>         self.do_handshake()
>       File "/usr/lib64/python2.7/ssl.py", line 833, in do_handshake
>         self._sslobj.do_handshake()
>     SSLError: [SSL: SSLV3_ALERT_BAD_CERTIFICATE] sslv3 alert bad certificate 
> (_ssl.c:579)
>     



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to