One more attempt: stuck processes
murch at andrew.cmu.edu
Fri Nov 16 12:58:49 EST 2007
Sebastian Hagedorn wrote:
> --On 16. November 2007 12:39:28 -0500 Ken Murchison
> <murch at andrew.cmu.edu> wrote:
>> Sorry, my patch wasn't complete. It wasn't logging the value that I
> Nov 16 18:48:17 lvr13 pop3s: SSL_read() returned 0:5
> Nov 16 18:48:33 lvr13 pop3s: SSL_read() returned 0:5
> Nov 16 18:48:50 lvr13 pop3s: SSL_read() returned 0:6
> Nov 16 18:48:54 lvr13 pop3s: SSL_read() returned 0:5
> Nov 16 18:49:03 lvr13 pop3s: SSL_read() returned 0:5
> Nov 16 18:49:11 lvr13 pop3s: SSL_read() returned 0:5
> Nov 16 18:49:38 lvr13 pop3s: SSL_read() returned 0:5
> Nov 16 18:49:54 lvr13 pop3s: SSL_read() returned 0:5
> I'm guessing that's still not enough:
> #define SSL_ERROR_SYSCALL 5 /* look at error stack/return
> value/errno */
> #define SSL_ERROR_ZERO_RETURN 6
> Some I/O error occurred. The OpenSSL error queue may contain
> information on the error. If the error queue is empty (i.e.
> ERR_get_error() returns 0), ret can be used to find out more
> the error: If ret == 0, an EOF was observed that violates the
> tocol. If ret == -1, the underlying BIO reported an I/O error
> socket I/O on Unix systems, consult errno for details).
> So should I add a call to ERR_get_error()?
Not yet. I'm assuming that none of these processes has hung. We're
getting an I/O error most likely because the client has closed the
connection immediately after sending QUIT. This is harmless.
What I really want to see is if we get a SSL_ERROR_WANT_xxx return code
when we're hung.
Project Cyrus Developer/Maintainer
Carnegie Mellon University
More information about the Info-cyrus