Skip site navigation (1) Skip section navigation (2)

Re: BUG #2829: Runaway logs - "SSL SYSCALL error"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Sean" <sean(dot)murphy(at)equipoint(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2829: Runaway logs - "SSL SYSCALL error"
Date: 2006-12-17 00:01:22
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
"Sean" <sean(dot)murphy(at)equipoint(dot)com> writes:
> The pg log files are the culprit - they fill up at a rate of about 50 megs a
> minute with lines reading
> "SSL SYSCALL error: A blocking operation was interrupted by a call to
> WSACancelBlockingCall."

We've seen this reported before...

> Is this a psql problem or a psqlODBC problem?

[ 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.

We could probably suppress the log-file-filling behavior by not
reporting duplicate messages (pqcomm.c has done that for a long
time, but there's no such logic in secure_write).  But really you
want a fix for the underlying bug, and I think for that you ought
to report it to the OpenSSL folk.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: HansDate: 2006-12-17 06:19:29
Subject: BUG #2834: installation problem
Previous:From: Tom LaneDate: 2006-12-16 23:15:17
Subject: Re: BUG #2830: Wrong results for prepared statements while clustering target table

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group