From: Tom Lane <tgl@sss.pgh.pa.us>
To: Arnold, Sandra L. <arnoldsl@ornl.gov>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: unexpected EOF on client connection during pg_dumpall
Date: Tue, 23 Jul 2013 19:29:44 -0400
Message-ID: <28964.1374622184@sss.pgh.pa.us> (raw)
In-Reply-To: <F7D6A12B572935439E34065CFADC851CE6A137519E@EXCHMBB.ornl.gov>
References: <F7D6A12B572935439E34065CFADC851CE6A137519E@EXCHMBB.ornl.gov>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
"Arnold, Sandra L." <arnoldsl@ornl.gov> writes:
> I am currently getting a "unexpected EOF on client connection" when
> running pg_dumpall from a bash shell script in cron. I have looked
> online to see if anyone else is having or have had this problem
> without any luck. I am hoping someone can point me in the right
> direction to determine what is happening. When I run the command
> manually it works.
That's really odd. The only theory that comes to mind is that there's
something different about the execution environment under cron, but it's
pretty hard to see how that would allow pg_dumpall to get as far as the
log shows and then crash. For instance, if you had a LD_LIBRARY_PATH
setting in your manual environment that wasn't shared by cron, that
could lead to pg_dumpall picking up the wrong copy of libpq.so and then
crashing --- but you'd really expect such a failure to happen at or near
the start of execution.
What I'd try next is (1) adding an "env" command to the cron shell
script so you can compare that environment to your regular shell,
and (2) adding "ulimit -c unlimited" to the shell script in hopes
of collecting a core dump you could get a stack trace from.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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: tgl@sss.pgh.pa.us, arnoldsl@ornl.gov
Subject: Re: unexpected EOF on client connection during pg_dumpall
In-Reply-To: <28964.1374622184@sss.pgh.pa.us>
* 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