From: | Scott Whitney <scott(at)journyx(dot)com> |
---|---|
To: | Dave Bolt <dave(at)davebolt(dot)co(dot)uk>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Failed to execute pg_dump |
Date: | 2018-01-03 19:14:51 |
Message-ID: | CY4PR11MB1575526BB540A62AD11C3AD0A71E0@CY4PR11MB1575.namprd11.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
My immediate thought is always permissions.
As whom a phpPgAdmin running? Probably the Apache user who may or may not have rights to see pg_dump.
________________________________
From: Dave Bolt <dave(at)davebolt(dot)co(dot)uk>
Sent: Wednesday, January 3, 2018 1:11 PM
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Failed to execute pg_dump
Hi Everyone
I have a test server which is running Centos7, PHP 7.1.13, PostgreSQL 9.6.5 and phpPgAdmin 5.1
When I went to dump a database I received the following error:
Export error: Failed to execute pg_dump (given path in your conf/config.inc.php : /opt/rh/rh-postgresql96/root/usr/bin/pg_dump). Please, fix this path in your configuration and relog.
The path /opt/rh/rh-postgresql96/root/usr/bin/pg_dump is valid.
I have checked the /user/share/phpPgAdmin/conf/config.inc.php which appears to be the configuration file mentioned in the error message and I can’t see any obvious issues.
I searched this problem in the mailing list but could not find any recent results. I did find an older result which said to correct the path in the config file, but that looks right to me.
Any ideas?
Thanks
Journyx, Inc.
7600 Burnet Road #300
Austin, TX 78757
www.journyx.com
p 512.834.8888
f 512-834-8858
Do you receive our promotional emails? Click here <http://journyx.com/communication-preferences> or visit http://journyx.com/communication-preferences to unsubscribe.
From | Date | Subject | |
---|---|---|---|
Next Message | Rui DeSousa | 2018-01-03 19:23:37 | Re: pt_toast table seems to be |
Previous Message | Dave Bolt | 2018-01-03 19:11:09 | Failed to execute pg_dump |