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

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

From: "Sean" <sean(dot)murphy(at)equipoint(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #2829: Runaway logs - "SSL SYSCALL error"
Date: 2006-12-15 16:07:17
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      2829
Logged by:          Sean
Email address:      sean(dot)murphy(at)equipoint(dot)com
PostgreSQL version: 8.2
Operating system:   W2K Server
Description:        Runaway logs - "SSL SYSCALL error"

A couple of times in the last month or two (first on an 8.0 installation,
now again after the upgrade) I've had the server get brought down by a full
hard drive. 

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

I have two different VB applications used by a couple of dozen employees to
access the db using SSL server and client certs via psqlODBC (build
unicode). One of the applications connects first as a low-privilege user to
check login credentials prior to connecting again as a privileged user. I
also have several web servers that connect using the JDBC driver WITHOUT SSL
on the local subnet, and a couple of administrators who use pgAdmin on the
local subnet.

The last few entries of the log before going nova were:
SSL SYSCALL error: No error
could not receive data from client: No error
unexpected EOF on client connection

Is this a psql problem or a psqlODBC problem? Is there a way that I can
modify the server not to log this particular error, or better yet, to log it
only once? Or even to die on this error (if it's going to crash on this, it
would be nice to do it without taking the entire server down with it).


pgsql-bugs by date

Next:From: Patrice BeliveauDate: 2006-12-15 19:26:07
Subject: lost on referentail integrity
Previous:From: Marek WróbelDate: 2006-12-15 09:01:11
Subject: Re: execute incorect query and get data

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