Bug #2213

(connections.c.1698) SSL (error): 5 -1 0 Success

Added by Olaf-van-der-Spek almost 10 years ago. Updated over 9 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Missing in 1.5.x:


My error.log is filled with lines like this. Doesn't look right...


Updated by Anonymous over 9 years ago

I can confirm this. This topic might be related:


Updated by stbuehler over 9 years ago

  • Target version changed from 1.4.27 to 1.4.x

Yes, I still think this isn't our fault.


Updated by Olaf-van-der-Spek over 9 years ago

In that case a link to the OpenSSL bug report would be nice. ;)


Updated by badmotorfinger over 9 years ago

It appears to be due to a change in OpenSSL 0.9.8m's SSL_shutdown call in non-blocking environments. Not sure if the damage is purely cosmetic or causing other misbehavior on socket shutdown.

So you're probably not going to see an OpenSSL bug on this one - they consider it to be a fix.


Updated by stbuehler over 9 years ago

  • Target version changed from 1.4.x to 1.4.27
  • Missing in 1.5.x changed from No to Yes

Let me repeat what happened if you get that error message:

SSL_shutdown failed, SSL_get_error returned SSL_ERROR_SYSCALL, but errno == 0

The things you linked describe that SSL_shutdown may fail with SSL_ERROR_WANT_{READ,WRITE} - but that is not happening here.

So i still consider this an openssl bug. As i don't care about stupid ssl shutdown errors (we are in the lighty connection error state too anyway), i will just silence the error now.


Updated by stbuehler over 9 years ago

  • Status changed from New to Fixed
  • % Done changed from 0 to 100

Applied in changeset r2749.

Also available in: Atom