Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eWpf1-0000B6-Hk for pgsql-admin@arkaria.postgresql.org; Wed, 03 Jan 2018 20:29:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eWpf0-0001wG-St for pgsql-admin@arkaria.postgresql.org; Wed, 03 Jan 2018 20:29:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eWpf0-0001w7-Kj for pgsql-admin@lists.postgresql.org; Wed, 03 Jan 2018 20:29:14 +0000 Received: from nativespace-chaldene.ns-chaldene.com ([212.53.86.59]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eWpew-00077h-Nf for pgsql-admin@lists.postgresql.org; Wed, 03 Jan 2018 20:29:14 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=davebolt.co.uk; s=default; h=Content-Type:MIME-Version:Message-ID:Date: Subject:In-Reply-To:References:To:From:Sender:Reply-To:Cc: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=6ghCWCd1Xz2YK5GVu/ToQbyLfp7DURskDwx8sHIZZko=; b=hb31M3E8MutojdakT08LTV473 yWiei+vUgeoRwZIftpDBv0FP3JSZcj5mC3n5zURn0njLh/XB81AiXajgiBtirq8sqL7Nr2un99kY6 47gOK3iDi2quxWBqAlwPSydtgSX/TLT15+8F8SGzj9NoMVs1ps3aKPOfUg1MPS2GREyVU=; Received: from 5.242.189.80.dyn.plus.net ([80.189.242.5]:49462 helo=BelongadaveX) by nativespace-chaldene.ns-chaldene.com with esmtpa (Exim 4.89_1) (envelope-from ) id 1eWpes-000Pou-BR for pgsql-admin@lists.postgresql.org; Wed, 03 Jan 2018 20:29:06 +0000 From: "Dave Bolt" To: References: <007a01d384c6$9d594260$d80bc720$@co.uk> In-Reply-To: Subject: RE: Failed to execute pg_dump Date: Wed, 3 Jan 2018 20:29:07 -0000 Message-ID: <009101d384d1$8128c380$837a4a80$@co.uk> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0092_01D384D1.8128C380" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdOExp0lXHdnlZw8SZG/hhCZYhemJwAAHAtaAAIhz+A= Content-Language: en-gb X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - nativespace-chaldene.ns-chaldene.com X-AntiAbuse: Original Domain - lists.postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - davebolt.co.uk X-Get-Message-Sender-Via: nativespace-chaldene.ns-chaldene.com: authenticated_id: dave@davebolt.co.uk X-Authenticated-Sender: nativespace-chaldene.ns-chaldene.com: dave@davebolt.co.uk List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0092_01D384D1.8128C380 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi Scot, Permissions on the pg_dump file are: -rwxr-xr-x for owner root, group root. If I go to the directory and execute as my normal user it seems to be working, at least for pg_dump --help From: Scott Whitney [mailto:scott@journyx.com] Sent: 03 January 2018 19:15 To: Dave Bolt; pgsql-admin@lists.postgresql.org Subject: Re: Failed to execute pg_dump 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 Sent: Wednesday, January 3, 2018 1:11 PM To: pgsql-admin@lists.postgresql.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 or visit http://journyx.com/communication-preferences to unsubscribe. ------=_NextPart_000_0092_01D384D1.8128C380 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Scot,

Permissions on the pg_dump file are:

-rwxr-xr-x for owner root, group root.

If I go to the directory and execute as my normal user it seems to be = working, at least for

pg_dump --help

 

 

From:= Scott = Whitney [mailto:scott@journyx.com]
Sent: 03 January 2018 = 19:15
To: Dave Bolt; = pgsql-admin@lists.postgresql.org
Subject: Re: Failed to = execute pg_dump

 

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@davebolt.co.uk>
Sen= t: Wednesday, January 3, 2018 1:11 PM
To: pgsql-admin@lists.postgr= esql.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 or visit = http://journyx.com/= communication-preferences to = unsubscribe.

------=_NextPart_000_0092_01D384D1.8128C380--