It does not write anything to stdout and stderr. The only thing I see is the error in the server's csv file. However, I got this to work by adding the following to the command line "su - postgres -c " and having the pg_dumpall command in double quotes. 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@xxxxxxxxx] Sent: Thursday, August 01, 2013 2:24 PM To: Arnold, Sandra L.; pgsql-admin@xxxxxxxxxxxxxx Subject: Re: unexpected EOF on client connection during pg_dumpall "Arnold, Sandra L." <arnoldsl@xxxxxxxx> 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 client had 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@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
