SSL_write() failed - v1.0.4

Server NGINX
1

Hello,

I am getting the following in my error.log file:

2011/09/22 14:09:19 [crit] 29589#0: *27891 SSL_write() failed (SSL:)
while sending to client, client: 187.32.96.60, server:
innovationgames.com, request: “GET
/game_view/instant_play/SECVSRHNYL3G5UZGCFSOP2455TURX25Q HTTP/1.1”,
upstream:
“http://127.0.0.1:9911/game_view/instant_play/SECVSRHNYL3G5UZGCFSOP2455TURX25Q”,
host: “innovationgames.com”, referrer:
“http://translate.googleusercontent.com/translate_c?hl=pt-BR&rurl=translate.google.com.br&sl=en&tl=pt&u=http://innovationgames.com/&usg=ALkJrhjEddqgpHPPquhnwql-3tdLHC5nDQ”

I am running nginx v1.0.4. I noticed another user (dryang) posted a
similar problem agains v0.7.67, but there was no further information on
that post.

I also notice the following post in the development forum
([PATCH] fix SSL handshake crit messages)
which indicated a patch but that was over a year and a half ago.

Any help very much appreciated.

Thanks for allowing me to post here.

Dan O’Leary
The Innovation Games Company

Posted at Nginx Forum:

2

Hello!

On Thu, Sep 22, 2011 at 05:02:18PM -0400, danieljoleary wrote:

“http://127.0.0.1:9911/game_view/instant_play/SECVSRHNYL3G5UZGCFSOP2455TURX25Q”,
host: “innovationgames.com”, referrer:

“http://translate.googleusercontent.com/translate_c?hl=pt-BR&rurl=translate.google.com.br&sl=en&tl=pt&u=http://innovationgames.com/&usg=ALkJrhjEddqgpHPPquhnwql-3tdLHC5nDQ”

I am running nginx v1.0.4. I noticed another user (dryang) posted a
similar problem agains v0.7.67, but there was no further information on
that post.

Are you able to reproduce this? If yes, please provide
debug log. See Debugging | NGINX for details.

I also notice the following post in the development forum
([PATCH] fix SSL handshake crit messages)
which indicated a patch but that was over a year and a half ago.

This post just mentions such errors as something
not-yet-identified, patch is unrelated and tunes logging level for
other common SSL errors.

Maxim D.

3

Hi Maxim,

I currently only have one instance of the error but expect there will be
more. To prepare for this, I will build a debug version of nginx and
set the log level to debug per the directions you have indicated. It
may be a while before I come back on this thread.

Thanks for your response!

Dan

Posted at Nginx Forum: