Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
SSL broken pipe
- From: Marc Cousin <mcousin(at)sigma(dot)fr>
- To: pgsql-admin(at)postgresql(dot)org
- Subject: SSL broken pipe
- Date: Wed, 28 Mar 2007 14:43:14 +0200
Hi, I've been having this problem occurring a few times in the last few days : in the postgresql log, I've seen these messages : 2007-03-28 13:53:34.845 CEST,18249 LOG: SSL SYSCALL error: Broken pipe 2007-03-28 13:53:34.846 CEST,18249 LOG: SSL SYSCALL error: Broken pipe 2007-03-28 13:53:34.846 CEST,18249 LOG: SSL SYSCALL error: Broken pipe 2007-03-28 13:53:34.846 CEST,18249 LOG: SSL SYSCALL error: Broken pipe 2007-03-28 13:53:34.847 CEST,18249 LOG: SSL SYSCALL error: Broken pipe 2007-03-28 13:53:34.847 CEST,18249 LOG: SSL SYSCALL error: Broken pipe 2007-03-28 13:53:34.847 CEST,18249 LOG: SSL SYSCALL error: Broken pipe 2007-03-28 13:53:34.848 CEST,18249 LOG: SSL SYSCALL error: Broken pipe 2007-03-28 13:53:34.848 CEST,18249 LOG: SSL SYSCALL error: Broken pipe As you can see, these messages are sent quite fast, and fill the filesystem quite rapidly. The server is postgresql 8.2.3 64 bits on debian unstable The client is pgadmin3 as provided with Postgresql 8.1.7 for Windows. I don't know what the client was doing exactly but I could investigate. Is this a known problem ? It's quite problematic, as it can fill a gigabyte of log file in a minute... Thanks in advance Marc
- Prev by Date: Re: set password doesn't work
- Next by Date: Investigating upgrading from version 8.0.1 to 8.2.3 to allow for easy replication and upgrades.
- Previous by thread: Strange behavior
- Next by thread: Investigating upgrading from version 8.0.1 to 8.2.3 to allow for easy replication and upgrades.
- Indexes: