[
https://issues.apache.org/jira/browse/MESOS-10218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17316185#comment-17316185
]
prasadkulkarni0711 commented on MESOS-10218:
--------------------------------------------
[~apeters]
openssl s_client -showcerts -connect <MASTER>:5050
here I see the certs but get this at the end:
Verify return code: 21 (unable to verify the first certificate)
openssl s_client -showcerts -connect <SLAVE>:5051
CONNECTED(00000003)
write:errno=0
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 283 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---
I don't see the certs on the slave
> Mesos slave fails to connect after enabling ssl
> -----------------------------------------------
>
> Key: MESOS-10218
> URL: https://issues.apache.org/jira/browse/MESOS-10218
> Project: Mesos
> Issue Type: Bug
> Components: agent
> Affects Versions: 1.9.0
> Reporter: prasadkulkarni0711
> Priority: Major
>
> Mesos agent fails to connect to the master after setting the following
> variables:
> LIBPROCESS_SSL_ENABLED=1
> LIBPROCESS_SSL_KEY_FILE=/etc/mesos/conf/ssl/server.key
> LIBPROCESS_SSL_CERT_FILE=/etc/mesos/conf/ssl/server.pem
> LIBPROCESS_SSL_REQUIRE_CERT=false
> LIBPROCESS_SSL_VERIFY_SERVER_CERT=false
> LIBPROCESS_SSL_REQUIRE_CLIENT_CERT=false
> LIBPROCESS_SSL_HOSTNAME_VALIDATION_SCHEME=openssl
> LIBPROCESS_SSL_VERIFY_CERT=false
> LIBPROCESS_SSL_CA_DIR=/etc/mesos/conf/ssl
> LIBPROCESS_SSL_CA_FILE=/etc/mesos/conf/ssl/ca.pem
> LIBPROCESS_SSL_SUPPORT_DOWNGRADE=false
> LIBPROCESS_SSL_VERIFY_IPADD=false
> #LIBPROCESS_SSL_ENABLE_TLS_V1_2=true
> Error in logs:
> Failed to accept socket: Failed accept: connection error: error:1407609C:SSL
> routines:SSL23_GET_CLIENT_HELLO:http request
> Connectivity works after setting:
> LIBPROCESS_SSL_SUPPORT_DOWNGRADE=true
> But then the sandbox fails to open in the web UI:
> Potential reasons:
> * The agent is not accessible
> * The agent timed out or went offline
> With the following error in the logs:
> Failed to recv on socket 38 to peer 'unknown': Failed recv, connection error:
> Connection reset by peer
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
