Re: unexpected EOF on client connection during pg_dumpall

Ok.  I thought I had fixed this problem but now it is back.  I separated my PostgreSQL backup job from my MySQL backup
joband am now executing it as follows:
 

su - postgres -c "/app/PostgreSQL/9.1/bin/pg_dumpall -h hostname -p 5432 -f
/DBbackups/postgres/postgres.bkp_$backupdate-U backup"
 

backupdate is being set prior to executing the command to the current date and time.

It is working for a while and does backup some of the database until I get the following:

2013-08-02 14:04:38:426 EDT,"backup","dbname",21315,"hostname:40356",51fbf3a2.5343.401,"idle in
transaction","2013-08-0214:00:02 EDT,3/299,0,LOG,08P01,"unexpected EOF on client connection",,,,,,,,,"pg_dump"
 
2013-08-02 14:04:38.426 EDT,"backup","dbname",21315,"hostname:40356",51fbf3a2.5343,402,"idle in
transaction","2013-08-0214:00:02 EDT,,0,LOG,00000,"disconnection:  session time:  0:04:36.044 user=backup
database=dbnamehost=hostname port=40356",,,,,,,,,"pg_dump"
 
2013-08-02 14:04:40.981 EDT,"backup","postgres",21309,"hostname:40353",51fbf3a1.533d,47,"idle",2013-08-02 14:00:01
EDT,2/0,0,LOG,08P01,"unexpectedEOF on client connection",,,,,,,,,"pg_dumpall"
 
2013-08-02 14:04:40.981 EDT,"backup","postgres",21309"hostname:40353",51fbf3a1.533d,48,"idle",2013-08-02 14:00:01
EDT,,0,LOG,00000,"disconnection:session time: 0:04:39.039 user=backup database=postgres host=hostname
port=40353",,,,,,,,,"pg_dumpall"

I have changed the hostname and the database name that was not the postgres database for security reasons.

It looks like it completed the COPY statement for the table that it was backing up right before the error message
occurred. I also do not see anything in the backup file that indicates what is happening.
 

The Postgresql version is 9.1.9 and is running on CENTOS 5.9.

Any help is appreciated.

Thanks,

Sandra Arnold
Database/Data Warehouse Administrator
MartinFederal Consulting
Consultant to Oak Ridge National Laboratory
Computational Data Analytics Group
Data Architectures Team


-----Original Message-----
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Arnold, Sandra L.
Sent: Thursday, August 01, 2013 2:29 PM
To: Kevin Grittner; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] unexpected EOF on client connection during pg_dumpall

It does not write anything to stdout and stderr.  The only thing I see is the error in the server's csv file.  However,
Igot this to work by adding the following to the command line "su - postgres -c " and having the pg_dumpall command in
doublequotes.  I was trying to run this as root but for some reason it did not like it.
 

Sandra Arnold
Database/Data Warehouse Administrator
MartinFederal Consulting
Consultant to Oak Ridge National Laboratory Computational Data Analytics Group Data Architectures Team

-----Original Message-----
From: Kevin Grittner [mailto:kgrittn@ymail.com]
Sent: Thursday, August 01, 2013 2:24 PM
To: Arnold, Sandra L.; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] unexpected EOF on client connection during pg_dumpall
"Arnold, Sandra L." <arnoldsl@ornl.gov> wrote:

> 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.

> Please let me know if I need to provide any other information.

What does pg_dumpall write to stdout and stderr?  I have only seen the server-side error you show when the pg_dumpall
clienthad an error writing, due to permissions problems or disk space exhaustion, and the reason needs to be found on
the"client" side, not in the server log.
 

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin