openSSL v9.8.2 on Windows 2000 Server in support of PostgreSQL 8.2 - my original bug report to the Postgres developers can be found at: http://archives.postgresql.org/pgsql-bugs/2006-12/msg00122.php
A follow-up to my report posted by Tom Lane, a member of Postgres' core dev team, includes the following: [quote] [ pokes around... ] I'm inclined to say it's an OpenSSL bug --- the message string corresponds to WSAEINTR, which to the extent I know anything about Windows (which is admittedly nil) seems like it should be treated the same as EINTR on Unix, ie, retry. That is how Postgres treats it on regular unsecured socket connections. But a look in the OpenSSL sources finds no indication that they treat it specially, which means they're going to think it's a hard error. [/quote] Basically, I've had my server brought down on three occasions by full hard drives. They fill with Postgres' log files, logging the error message: "SSL SYSCALL error: A blocking operation was interrupted by a call to WSACancelBlockingCall." As I understand Tom's follow-up to my bug report, some part of my client-server interaction is causing what should be a soft error, but OpenSSL reports it to Postgres as a hard error, and Postgrs in turn dutifully logs it... again and again and again. Exactly what initiates the problem is totally beyond me, but the circumstances are that my typical user is running two db-connected applications at a time - one that creates an SSL encrypted ODBC session and leaves the connection open all day, and another that gets used on and off throughout the day, first establishing an SSL ODBC session to authenticate the user and then closing that connection and opening another if authentication succeeds. All of these connections use the same client certificate (per user, anyway) and connect to the same data server. I have a couple dozen users who use this setup every day without incident, but periodically the bug situation occurs causing headaches all around. I haven't yet been able to identify any common thread (in terms of who's doing/attempting to do what when it happens) between the three incidents. I don't know if any of this helps; if there is additional information that would help to better zero in on the problem let me know. Thanks for any attention you are able to give. Sean Murphy ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
