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

Dmitry Sen updated AMBARI-2389:
-------------------------------

    Attachment: AMBARI-2389.patch

Attached patch.

After applying of the patch:
1. In case of not related to ssl network connectivity issues, the agent 
repeatedly tries to reconnect to the ambari-server
2. In case of agent certificate signing failure, the agent logs(Certificate 
signing failed. \nIn order to receive a new agent certificate, remove existing 
certificate file from keys directory. As a workaround you can turn off two-way 
SSL authentication in server configuration(ambari.properties) \nExiting..) and 
exits.
3. In case of other ssl related issues, the agent logs(Two-way SSL 
authentication failed. Ensure that server and agent certificates were signed by 
the same CA and restart the agent. \nIn order to receive a new agent 
certificate, remove existing certificate file from keys directory. As a 
workaround you can turn off two-way SSL authentication in server 
configuration(ambari.properties) \nExiting..) and exits.

                
> Registration fails sometimes because of openssl issues on signing the certs.
> ----------------------------------------------------------------------------
>
>                 Key: AMBARI-2389
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2389
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.2.0
>            Reporter: Dmitry Sen
>            Assignee: Dmitry Sen
>            Priority: Critical
>             Fix For: 1.3.0
>
>         Attachments: AMBARI-2389.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Registration fails sometimes because of openssl issues on signing the certs. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to