If it is returning SSL_ERROR_SYSCALL, you need to examine the value of errno, possibly with perror().
Basically, the library is returning this because the underlying OS has signalled (via errno) that some system call has failed with an error condition. If you don't understand what could be causing this, I would suggest running strace, truss, or some other system-call tracing utility to see what the system is doing. -Kyle H On Thu, Mar 26, 2009 at 10:40 AM, Vivek Mathew -X (vivmathe - WIPRO at Cisco) <vivma...@cisco.com> wrote: > Hi, > > Our application was previously making use of the OpenSSL 0.9.7d library. > > Recently we have upgraded to the 0.9.8j version and have re-built both the > Client and Server executables. > However, after the upgrade we are facing a problem with the client side > failing to connect to the server. After investigating this a little more, we > found that the call to SSL_connect() function is failing on the Client Side. > The Returned value for this function call is 0. > > ************************************************* > result = SSL_connect(m_ssl); > errCode = SSL_get_error(m_ssl,result); > ************************************************* > > When I retieved the error code by calling SSL_get_error() function, I am > getting the value "SSL_ERROR_SYSCALL". (So in my code result=0 and > errCode=SSL_ERROR_SYSCALL). > > Can somebody please guide me about any known issues with SSL_connect() > function, in 0.9.8j version of SSL? > Also, if there is something which I can try, so as to correct this error and > get my software to work as before? > > Any help would be very much appreciated. > > - Vivek ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
