From: Torsten Luettgert <t.luettgert@pressestimmen.de>
To: pgsql-admin@postgresql.org
Subject: Re: reindexdb dying with SIGPIPE on 8.2.5
Date: Sun, 10 Aug 2008 16:15:50 +0200
Message-ID: <1218377750.3421.7.camel@murdegern.cbxnet.de> (raw)
In-Reply-To: <20908.1218080249@sss.pgh.pa.us>
References: <1218035421.19154.24.camel@oberschatzi.cff>
<20908.1218080249@sss.pgh.pa.us>
On Wed, 2008-08-06 at 23:37 -0400, Tom Lane wrote:
> I'm wondering if the reindexdb is being run under a restrictive ulimit
> setting, or something else that would prevent it from just sitting and
> waiting.
I checked... there's no limits defined in /etc/security/limits.conf.
There's more weirdness here: on the same machine, one day, everything
runs through fine.
Another day, one or two DBs are reindexed and vacuumed properly, then
all successive tries fail with the mentioned SIGPIPE error.
I'll have STDOUT and STDERR redirected to a file before the call of
reindexdb now. Perhaps there's something in the console output that
helps.
> Is there anything in the kernel log at the time of the failure report?
Don't see anything except postgresql messages at that time
in /var/log/messages, and nothing at all in /var/log/secure.
Regards,
Torsten
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: t.luettgert@pressestimmen.de
Subject: Re: reindexdb dying with SIGPIPE on 8.2.5
In-Reply-To: <1218377750.3421.7.camel@murdegern.cbxnet.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox