SSL_read() returning SSL_ERROR_SYSCALL with errno 11EAGAIN

Erik Forsberg erik at
Tue Apr 30 22:41:59 UTC 2019

>-- Original Message --
>On Tue, Apr 30, 2019 at 03:23:23PM -0700, Erik Forsberg wrote:
>> >Is the handshake explicit, or does the application just call
>> >SSL_read(), with OpenSSL performing the handshake as needed?
>> I occasionally (somewhat rarely) see the issue mentioned by the OP.
>> Ignoring the error, or mapping it and do what WANT_READ/WANT_WRITE
>> does effectively hides the issue and connection works fine. I predominantly
>> run on Solaris 11. In my case, I open the socket myself, set non-blocking
>> mode and associates with an SSL object using SS_set_fd().
>> The initial handshake is done explicitly.
>Recoverable errors should not result in SSL_ERROR_SYSCALL.  This
>feels like a bug.  I'd like to hear from Matt Caswell on this one.
>Perhaps someone should open an issue on Github...
I will scan my logs later this evening and see if this is still an issue.
Last time I remember seeing it was quote some long time ago (couple of years)

More information about the openssl-users mailing list