From: Sebastian Tennant <sebyte@smolny.plus.com>
To: guile-user@gnu.org
Subject: Broken pipe errors using guile-pg with guile 1.8
Date: Mon, 23 Feb 2009 16:57:21 +0000 [thread overview]
Message-ID: <bpstgkge.fsf@vps203.linuxvps.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
Hi Guilers,
Is anyone familiar with the internals of guile-pg (version 0.16, author
Ian Grant) which wraps PostgreSQL's libpq?
I'm getting a lot of 'broken pipe' errors of the sort:
Feb 23 11:32:13 stderr: ERROR: In procedure pg-connectdb:
Feb 23 11:32:13 stderr: ERROR: could not send startup packet: Broken pipe
It's especially bad at times of light load (rather than no load) and I
never once noticed this error whilst the webapp was in development
(i.e., I was the only person using it) which suggests to me that it's
happening whenever two or more page requests call scripts that attempt
to open database connections more or less at the same time.
All my calls to pg-connectdb are let bound so database connections are
(supposed to be) closed after every query.
Any advice very much appreciated. I've attached a log extract to give
you an idea of the frequency of failures. I need to find a solution to
this problem fast!
Seb
P.S. Perhaps upgrading guile-pg is the first thing I should try? IIRC
there's a more recent pkgsrc version (which is guile 1.8
comaptible) somewhere... hunting for it now.
[-- Attachment #2: broken_pipes.txt --]
[-- Type: text/plain, Size: 9277 bytes --]
Feb 23 11:32:12 session.scm: Called...
Feb 23 11:32:12 session.scm: Called...
Feb 23 11:32:13 stderr: ERROR: In procedure pg-connectdb:
Feb 23 11:32:13 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 11:32:13 home: home.scm: EXITED WITH CODE 1
Feb 23 11:32:13 listing-view: listing-view.scm: exited cleanly
Feb 23 11:32:13 listing-view: #
--
Feb 23 11:43:27 home: calling home.scm...
Feb 23 11:43:27 session.scm: Called...
Feb 23 11:43:27 stderr: ERROR: In procedure pg-connectdb:
Feb 23 11:43:27 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 11:43:27 home: home.scm: EXITED WITH CODE 1
Feb 23 11:43:27 home: #
Feb 23 11:43:40 listing-view: calling listing-view.scm...
Feb 23 11:43:40 session.scm: Called...
Feb 23 11:43:40 session.scm: User peteksirin has just logged in.
Feb 23 11:43:40 stderr: ERROR: In procedure pg-connectdb:
Feb 23 11:43:40 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 11:43:40 listing-view: listing-view.scm: EXITED WITH CODE 1
Feb 23 11:43:40 listing-view: #
Feb 23 11:43:44 listing-view: calling listing-view.scm...
--
Feb 23 11:44:13 session.scm: Called...
Feb 23 11:44:13 session.scm: User peteksirin has just logged in.
Feb 23 11:44:13 stderr: ERROR: In procedure pg-connectdb:
Feb 23 11:44:13 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 11:44:13 listing-view: listing-view.scm: EXITED WITH CODE 1
Feb 23 11:44:14 listing-view: #
Feb 23 11:44:16 listing-view: calling listing-view.scm...
--
Feb 23 11:44:30 account-remind-form-handler.scm: Called...
Feb 23 11:44:30 account-remind-form-handler.scm: Form checks passed.
Feb 23 11:44:30 stderr: ERROR: In procedure pg-connectdb:
Feb 23 11:44:30 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 11:44:30 account-remind: account-remind.scm: EXITED WITH CODE 1
Feb 23 11:44:30 account-remind-form-handler.scm: Address is in use, account details exist. Sending reminder...
Feb 23 11:44:30 account-remind: #
--
Feb 23 11:45:37 account-remind: calling account-remind.scm...
Feb 23 11:45:37 session.scm: Called...
Feb 23 11:45:37 stderr: ERROR: In procedure pg-connectdb:
Feb 23 11:45:37 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 11:45:37 account-remind-form-handler.scm: Called...
Feb 23 11:45:37 account-remind-form-handler.scm: Form checks passed.
Feb 23 11:45:37 account-remind-form-handler.scm: Address is in use, account details exist. Sending reminder...
--
Feb 23 11:46:10 home: calling home.scm...
Feb 23 11:46:10 session.scm: Called...
Feb 23 11:46:10 stderr: ERROR: In procedure pg-connectdb:
Feb 23 11:46:10 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 11:46:10 home: home.scm: EXITED WITH CODE 1
Feb 23 11:46:10 home: #
Feb 23 11:46:12 listing-view: calling listing-view.scm...
--
Feb 23 11:46:19 home: calling home.scm...
Feb 23 11:46:19 session.scm: Called...
Feb 23 11:46:19 stderr: ERROR: In procedure pg-connectdb:
Feb 23 11:46:19 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 11:46:19 home: home.scm: EXITED WITH CODE 1
Feb 23 11:46:19 home: #
Feb 23 11:46:25 listing-view: calling listing-view.scm...
--
Feb 23 11:47:22 session.scm: User peteksirin is logged in.
Feb 23 11:47:22 session.scm: Called...
Feb 23 11:47:22 stderr: ERROR: In procedure pg-connectdb:
Feb 23 11:47:22 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 11:47:22 listing-browse: listing-browse.scm: EXITED WITH CODE 1
Feb 23 11:47:23 listing-view: listing-view.scm: exited cleanly
Feb 23 11:47:23 listing-view: #
--
Feb 23 11:47:45 session.scm: Called...
Feb 23 11:47:45 session.scm: User peteksirin is logged in.
Feb 23 11:47:45 stderr: ERROR: In procedure pg-connectdb:
Feb 23 11:47:45 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 11:47:45 home: home.scm: EXITED WITH CODE 1
Feb 23 11:47:45 rates-rationale: rates-rationale.scm: exited cleanly
Feb 23 11:47:45 rates-rationale: #
--
Feb 23 11:48:40 home: calling home.scm...
Feb 23 11:48:40 session.scm: Called...
Feb 23 11:48:40 stderr: ERROR: In procedure pg-connectdb:
Feb 23 11:48:40 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 11:48:40 home: home.scm: EXITED WITH CODE 1
Feb 23 11:48:40 home: #
Feb 23 11:48:52 listing-browse: calling listing-browse.scm...
--
Feb 23 11:49:52 home: calling home.scm...
Feb 23 11:49:52 session.scm: Called...
Feb 23 11:49:52 stderr: ERROR: In procedure pg-connectdb:
Feb 23 11:49:52 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 11:49:52 home: home.scm: EXITED WITH CODE 1
Feb 23 11:49:52 home: #
Feb 23 11:50:11 home: calling home.scm...
Feb 23 11:50:11 session.scm: Called...
Feb 23 11:50:11 stderr: ERROR: In procedure pg-connectdb:
Feb 23 11:50:11 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 11:50:11 home: home.scm: EXITED WITH CODE 1
Feb 23 11:50:11 home: #
Feb 23 11:50:29 listing-browse: calling listing-browse.scm...
Feb 23 11:50:29 session.scm: Called...
Feb 23 11:50:30 stderr: ERROR: In procedure pg-connectdb:
Feb 23 11:50:30 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 11:50:30 listing-browse: listing-browse.scm: EXITED WITH CODE 1
Feb 23 11:50:30 listing-browse: #
Feb 23 11:50:46 listing-view: calling listing-view.scm...
--
Feb 23 11:51:13 home: calling home.scm...
Feb 23 11:51:14 session.scm: Called...
Feb 23 11:51:14 stderr: ERROR: In procedure pg-connectdb:
Feb 23 11:51:14 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 11:51:14 home: home.scm: EXITED WITH CODE 1
Feb 23 11:51:14 home: #
Feb 23 11:51:26 listing-view: calling listing-view.scm...
--
Feb 23 11:52:20 home: calling home.scm...
Feb 23 11:52:20 session.scm: Called...
Feb 23 11:52:20 stderr: ERROR: In procedure pg-connectdb:
Feb 23 11:52:20 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 11:52:20 home: home.scm: EXITED WITH CODE 1
Feb 23 11:52:21 home: #
Feb 23 11:53:08 home: calling home.scm...
Feb 23 11:53:08 session.scm: Called...
Feb 23 11:53:08 stderr: ERROR: In procedure pg-connectdb:
Feb 23 11:53:08 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 11:53:08 home: home.scm: EXITED WITH CODE 1
Feb 23 11:53:08 home: #
Feb 23 11:54:23 listing-view: calling listing-view.scm...
--
Feb 23 11:57:50 stderr: 35: 3* [pg-connectdb "dbname=itidb"]
Feb 23 11:57:50 stderr:
Feb 23 11:57:50 stderr: zlib/listing-pgutils.scm:35:18: In procedure pg-connectdb in expression (pg-connectdb "dbname=itidb"):
Feb 23 11:57:50 stderr: zlib/listing-pgutils.scm:35:18: could not send startup packet: Broken pipe
Feb 23 11:57:50 stderr: ABORT: (misc-error)
Feb 23 11:58:21 stderr:
Feb 23 11:58:21 stderr: In standard input:
--
Feb 23 12:09:16 account-create-submission-handler.scm: Empty value checks passed and chosen username not in use.
Feb 23 12:09:16 account-create-submission-handler.scm: Email address xxx@xxx.xxx in use, but without a username. Performing sql UPDATE...
Feb 23 12:09:16 stderr: ERROR: In procedure pg-connectdb:
Feb 23 12:09:16 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 12:09:16 account-create: account-create.scm: EXITED WITH CODE 1
Feb 23 12:09:16 account-create-submission-handler.scm: Done.
Feb 23 12:09:17 account-create: #
--
Feb 23 12:13:07 account-create-submission-handler.scm: Called...
Feb 23 12:13:07 account-create-submission-handler.scm: Empty value checks passed and chosen username not in use.
Feb 23 12:13:07 stderr: ERROR: In procedure pg-connectdb:
Feb 23 12:13:07 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 12:13:07 account-create: account-create.scm: EXITED WITH CODE 1
Feb 23 12:13:07 account-create-submission-handler.scm: Email address xxx@xxx.xxx not in use. Performing sql INSERT...
Feb 23 12:13:08 account-create: #
--
Feb 23 15:52:26 home: calling home.scm...
Feb 23 15:52:26 session.scm: Called...
Feb 23 15:52:26 stderr: ERROR: In procedure pg-connectdb:
Feb 23 15:52:26 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 15:52:26 home: home.scm: EXITED WITH CODE 1
Feb 23 15:52:26 home: #
Feb 23 15:53:33 listing-view: calling listing-view.scm...
--
Feb 23 16:09:35 session.scm: Called...
Feb 23 16:09:35 account-create-submission-handler.scm: Called...
Feb 23 16:09:35 stderr: ERROR: In procedure pg-connectdb:
Feb 23 16:09:35 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 16:09:35 account-create: account-create.scm: EXITED WITH CODE 1
Feb 23 16:09:35 account-create-submission-handler.scm: Empty value checks passed and chosen username not in use.
Feb 23 16:09:35 account-create-submission-handler.scm: Email address xxx@xxx.xxx in use, but without a username. Performing sql UPDATE...
--
Feb 23 16:11:49 account-create-submission-handler.scm: Called...
Feb 23 16:11:49 account-create-submission-handler.scm: Empty value checks passed and chosen username not in use.
Feb 23 16:11:49 stderr: ERROR: In procedure pg-connectdb:
Feb 23 16:11:49 stderr: ERROR: could not send startup packet: Broken pipe
Feb 23 16:11:49 account-create: account-create.scm: EXITED WITH CODE 1
Feb 23 16:11:49 account-create-submission-handler.scm: Email address xxx@xxx.xxx in use, but without a username. Performing sql UPDATE...
Feb 23 16:11:50 account-create: #
[-- Attachment #3: Type: text/plain, Size: 135 bytes --]
--
Emacs' AlsaPlayer - Music Without Jolts
Lightweight, full-featured and mindful of your idyllic happiness.
http://home.gna.org/eap
next reply other threads:[~2009-02-23 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 16:57 Sebastian Tennant [this message]
2009-02-23 17:06 ` Broken pipe errors using guile-pg with guile 1.8 Greg Troxel
2009-02-23 18:53 ` Sebastian Tennant
2009-02-23 23:44 ` Greg Troxel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bpstgkge.fsf@vps203.linuxvps.org \
--to=sebyte@smolny.plus.com \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).