| From: | Marc Cousin <mcousin(at)sigma(dot)fr> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | SSL broken pipe |
| Date: | 2007-03-28 12:43:14 |
| Message-ID: | 200703281443.14234.mcousin@sigma.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chuck Amadi | 2007-03-28 13:23:07 | Investigating upgrading from version 8.0.1 to 8.2.3 to allow for easy replication and upgrades. |
| Previous Message | Phillip Smith | 2007-03-28 03:08:25 | Re: set password doesn't work |