Help: SSL_write returns SSL_ERROR_SYSCALL, EOF on Second Call

[ypankaj]

Hi All,

I am facing issue in my OPENSSL code. I have written openssl client. It sends request to the host and receives response for that request.

My problem is, it connects, sends request successfully to host at first time only in sencond attempt it fails on SSL_write(). where SSL_get_error() returns SSL_ERROR_SYSCALL error.

In that ERR_get_error() returns 0. man page shows "If ret == 0, an EOF was observed that violates the protocol".

Is anybody help me on this. How i can fix this.

Code Snippet.

w=SSL_write(SSLRequestData.ssl,c2s,c2sl);

switch(SSL_get_error(SSLRequestData.ssl,w))
{
case SSL_ERROR_NONE:
if(c2sl!=w)
{
wRetVal = SSL_INCOMPLETE_WRITE;
SSLConnect_Flag = FALSE;
LOG_PRINTF("SSL Error: SSL_INCOMPLETE_WRITE\n");
}
else
{
wRetVal = SUCCESS;
LOG_PRINTF("SSL: SSL Write SUCCESS\n");
}
break;

case SSL_ERROR_WANT_READ:
LOG_PRINTF("############## SSL_ERROR_WANT_READ \n");
break;

case SSL_ERROR_WANT_WRITE:
LOG_PRINTF("############## SSL_ERROR_WANT_WRITE \n");
break;

case SSL_ERROR_WANT_CONNECT:
LOG_PRINTF("############## SSL_ERROR_WANT_CONNECT \n");
break;

case SSL_ERROR_WANT_ACCEPT:
LOG_PRINTF("############## SSL_ERROR_WANT_ACCEPT \n");
break;

case SSL_ERROR_WANT_X509_LOOKUP:
LOG_PRINTF("############## SSL_ERROR_WANT_X509_LOOKUP \n");
break;

case SSL_ERROR_SYSCALL:
LOG_PRINTF("############## SSL_ERROR_SYSCALL \n");
iRetVal=ERR_get_error();
LOG_PRINTF("### ERR_get_error: %d\n", iRetVal);
break;

case SSL_ERROR_SSL:
LOG_PRINTF("############## SSL_ERROR_SSL \n");
break;

default:
wRetVal = SSL_WRITE_ERROR;
break;
}

if(wRetVal == SUCCESS)
{
LOG_PRINTF("Calling SSL_read..\n");

/* set transaction timer */
txnTimerId = CreateTimer(lTxnTimeout, Txn_TimerCallback, NULL);

do
{
r=SSL_read(SSLRequestData.ssl,s2c,NUM_OF_BYTES);
------
------


Please help on this!

[kcinmumbai]

check the code flow after first "success". Is it resetting anything - ctx, etc?

Also.. check if you're reading only part buffer OR if there are any loss of packet-level data in your program

[Rubberman]

My guess is that the reader has closed its end of the connection, hence the EOF being detected by the writer.

[ypankaj]

Thanks kcinmumbai & Rubberman for your replies.

Yes Rubberman, it's issue of server side, It was fixed.

[Shisya]

Thanks kcinmumbai & Rubberman for your replies.

Yes Rubberman, it's issue of server side, It was fixed.

Hi Pankaj,

Can you please disclose what was the issue on server side.

[oz]

Hello and welcome to the forums, Shisya!

This thread is almost 2 years old so I'm going to go ahead and close it, but please feel free to start a fresh thread of your own with some details if you are having any problems with Linux.

Thank you.