pg_dumpall not working?

David Siebert wrote:

Okay I have version 8.0.2 installed on CentOS 4.0 with all updates.
I SSH into the server and try and run pg_dump all and get a stream of
errors on the server screen but not on my ssh.
Any suggestions?

Um - post some of the errors?

There are some very clever people on these lists, but none of them
psychic afaik ;-)

--
Richard Huxton
Archonet Ltd

Um - post some of the errors?

There are some very clever people on these lists, but none of them
psychic afaik ;-)

Speak for yourself. I know you are wearing a blue shirt today! ;P)

Sincerely,

Joshua D. Drake

--
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/

Richard Huxton wrote:

David Siebert wrote:

Okay I have version 8.0.2 installed on CentOS 4.0 with all updates.
I SSH into the server and try and run pg_dump all and get a stream of
errors on the server screen but not on my ssh.
Any suggestions?

Um - post some of the errors?

There are some very clever people on these lists, but none of them
psychic afaik ;-)

Getting the errors is very difficult or I would have posted them. The
server does not have a mail client set up yet and the errors only show
on the servers screen not on the SSH screen.
The problem turned out to be SELinux.
There seems to be a policy that blocks pg_dumpall from working no matter
what user I am logged in as.
For now since it is a test system behind a firewall I will just turn off
SELinux until I can take the time to learn that part of Linux.

Richard Huxton wrote:

David Siebert wrote:

Okay I have version 8.0.2 installed on CentOS 4.0 with all updates.
I SSH into the server and try and run pg_dump all and get a stream of
errors on the server screen but not on my ssh.
Any suggestions?

Um - post some of the errors?

There are some very clever people on these lists, but none of them
psychic afaik ;-)

I would if I could. The errors where only showing on the server monitor
none where making it to the ssh client.
I discovered the problem was SELinux.

David Siebert <david@eclipsecat.com> writes:

Okay I have version 8.0.2 installed on CentOS 4.0 with all updates.
I SSH into the server and try and run pg_dump all and get a stream of
errors on the server screen but not on my ssh.

What do you get from

ls -Z /usr/bin/pg_dumpall
ls -Z /usr/bin/pg_dump

? On a reasonably up-to-date Fedora Core 3 system I get

-rwxr-xr-x root root system_u:object_r:bin_t /usr/bin/pg_dumpall
-rwxr-xr-x root root system_u:object_r:bin_t /usr/bin/psql

but it sounds a lot like you have something else, like postgresql_exec_t
(which is set up to forbid writes to /dev/tty, I believe). If so, try
restorecon on these files to see if that fixes it. If not, you have an
out-of-date SELinux policy RPM ... update that, or complain to CentOS
that they haven't borrowed Red Hat's latest version yet ;-)

regards, tom lane

Thanks for the help but it was an SELinux policy problem.
I turned it off for now. I just do not have the time to learn SELinux
right now and my server is located behind a fire wall, contains not
sensitive data, and is just a test box for now.

Tom Lane wrote: