Re: Troubleshooting Mesos SSL setup

[Renan DelValle <re...@gmail.com>]

No bugs as far as we can tell. The error message just wasn't very helpful
in this case. Seems like this is coming straight from the libevent library
in this case so I don't know if there's much that can be done from the
Mesos side.

In any case, I appreciate the follow up!

-Renan

On Tue, Apr 10, 2018 at 1:15 PM, Benjamin Mahler <bm...@apache.org> wrote:

> Are there bugs here? Is there anything that mesos could have logged /
> handled better?
>
> On Fri, Mar 16, 2018 at 11:46 AM, Renan DelValle <renanidelvalle@gmail.com
> > wrote:
>
>> Follow up,  we weren't able to get our wildcard certificate working but
>> we did get it to work when we used a certificate for a single hostname.
>>
>> Also our hostname was too long (over 64 bytes).
>>
>> Hope that helps someone else who runs into this issue.
>>
>> -Renan
>>
>> On Fri, Mar 16, 2018 at 10:36 AM, Renan DelValle <
>> renanidelvalle@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> We're trying to set up Mesos with SSL. We've compiled Mesos with SSL
>>> support and deployed it to the right boxes.
>>>
>>> Unfortunately, after setting up all the correct environmental variables,
>>> we get the following error:
>>>
>>> I0315 17:48:30.541865    20 libevent_ssl_socket.cpp:1105] Could not
>>>> determine hostname of peer: Unknown error
>>>> I0315 17:48:30.541937    20 libevent_ssl_socket.cpp:1120] Failed
>>>> accept, verification error: Cannot verify peer certificate: peer hostname
>>>> unknown
>>>> * GnuTLS recv error (-110): The TLS connection was non-properly
>>>> terminated.
>>>> * Closing connection 0
>>>> curl: (56) GnuTLS recv error (-110): The TLS connection was
>>>> non-properly terminated.
>>>
>>>
>>> Any chance someone knows what these errors mean and how we can fix the
>>> underlying issue?
>>>
>>> Thanks!
>>>
>>> -Renan
>>>
>>
>>
>