I don't know what the cause is, yet... I was hoping that the information
you gave me would give me some ideas :)

I've used it on RedHat 6.2 with OpenSSL 0.9.6b, but have never seen this
message before, so we'll have to see if we can get OpenSSL to tell us
what's wrong...

Here's a patch that will make sslstream.c write all of the error info
that it has to the trace file:

--- tn5250-0.16.3/src/sslstream.c       Wed Oct 31 17:29:23 2001
+++ sslstream.c Thu Jan 31 23:03:13 2002
@@ -978,6 +978,9 @@
                       return -1;
+                      TN5250_LOG(("debug: SSL_read error:  rc=%d, "
+                           "errnum=%d, errno=%d\n", rc, errnum, errno));
+                      DUMP_ERR_STACK ();
                       return -2;

After applying the patch, do a new "make" and "make install", then create
a new trace file by running tn5250 like this:

           tn5250 trace=/path/to/trace.txt ssl:as400.example.com

Then, if that doesn't help you figure out the problem, please E-mail me
the trace file (privately -- do _not_ send it to the mailing list) and I'll
do my best to try to get to the bottom of the problem.

On Thu, 31 Jan 2002, tushar m wrote:

> I am running the code on red hat linux version 6.2
> Openssl version is 0.9.6b and the tn5250 code i
> downloaded from the sourceforge.net site..version
> tn5250-0.16.3. yes I am looking into the trace file
> also. I would appreciate if u could give me some idea
> of what might be the causes !!
> > > values i get a SSL_read error...SSL_ERROR_SYSCALL
> > > in the function ssl_stream_get_byte(). I checked the
> > > return value from ERR_get_error() ..which returns
> > > a 0.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2021 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.