Stale global SSL error

Should I be worried about the following:

ignoring stale global SSL error (SSL: error:140D5042:SSL
routines:SSL3_CTRL:called a function you should not call) while reading
client request line

On Sat, Mar 22, 2008 at 11:33:23PM -0400, Ian M. Evans wrote:

Should I be worried about the following:

ignoring stale global SSL error (SSL: error:140D5042:SSL
routines:SSL3_CTRL:called a function you should not call) while reading
client request line

Yes, report any errors about “ignoring stale global SSL error”.
Although, nginx should work correctly even with this alert,
but it’s required to see unhandled errors in other place.

As to the case, it seems that nginx was built against OpenSSL 0.9.7,
but now it’s used with OpenSSL 0.9.8. Try to rebuild nginx against
current OpenSSL.

On Sun, March 23, 2008 4:36 am, Igor S. wrote:

As to the case, it seems that nginx was built against OpenSSL 0.9.7,
but now it’s used with OpenSSL 0.9.8. Try to rebuild nginx against
current OpenSSL.

Igor,

Upgraded to openssl 0.98.g and recompiled nginx. Still getting:

13053#0: *117 ignoring stale global SSL error (SSL: error:140D5042:SSL
routines:SSL3_CTRL:called a function you should not call) while reading
client request line

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs