Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eX5WM-0001PV-PE for pgsql-admin@arkaria.postgresql.org; Thu, 04 Jan 2018 13:25:23 +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 1eX5WL-0004DD-4p for pgsql-admin@arkaria.postgresql.org; Thu, 04 Jan 2018 13:25:21 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eX5WK-0004CE-O4 for pgsql-admin@lists.postgresql.org; Thu, 04 Jan 2018 13:25:20 +0000 Received: from nativespace-chaldene.ns-chaldene.com ([212.53.86.59]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eX5WE-0000K7-Tw for pgsql-admin@lists.postgresql.org; Thu, 04 Jan 2018 13:25:19 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=davebolt.co.uk; s=default; h=Content-Transfer-Encoding:Content-Type: MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:To:From:Sender: Reply-To:Cc: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=cICensjad1dnKDxD3BeRL3Cwd7fX+PVpRSNXwi0wOe0=; b=p9ZcjWWdLoNOyN+s87BCGABjor f+wbATXaUT2T/aNbVUTs3Kslq2MmIOxO/199qW4XM4EWi89m1u4oJrD7YM95IXqPOz1nW9xCY3Drw ru5GDDOQKCs83j114y+V3AZRmdtHpF+0crR5VMan6KYGdbzgiFLzZUYbFi7Zxz1ZuiPk=; Received: from 5.242.189.80.dyn.plus.net ([80.189.242.5]:59171 helo=BelongadaveX) by nativespace-chaldene.ns-chaldene.com with esmtpa (Exim 4.89_1) (envelope-from ) id 1eX5WA-000MdX-IP for pgsql-admin@lists.postgresql.org; Thu, 04 Jan 2018 13:25:10 +0000 From: "Dave Bolt" To: References: <007a01d384c6$9d594260$d80bc720$@co.uk> <009101d384d1$8128c380$837a4a80$@co.uk> In-Reply-To: Subject: RE: Failed to execute pg_dump Date: Thu, 4 Jan 2018 13:25:09 -0000 Message-ID: <007501d3855f$71cffdc0$556ff940$@co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdOE09H/njdNQnbrTtm1QL/xQAXkngAD+IOA 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 Apologies to Carlos for replying directly to him instead of to the list. Both php.ini files on my system have disable_functions =3D I set the permissions to 0x777 on pg_dump but that has not made any = difference. I also set sudo to permissive, which also does not seem to have helped. Unless I'm missing something, I think that covers all the suggestions = from Carlos, Scott and Nick (who's message doesn't seem to be included = below for some reason). Thanks for your suggestions, I'm learning things = anyway :) Dave -----Original Message----- From: Carlos Martinez [mailto:camarti@gmail.com]=20 Sent: 03 January 2018 20:44 To: pgsql-admin@lists.postgresql.org Subject: Re: Failed to execute pg_dump Hi. The problem can be caused by: 1) SELinux: may be you need set the options httpd_execmem or = httpd_can_network_connect_db. You can disable SELinux temporay with = setenfoce 0. 3) Review the option disable_functions on PHP: make sure that exec = family in not disabled. Best regards. Carlos M. On Wed, Jan 3, 2018 at 3:36 PM, Scott Whitney wrote: > It seems like the Apache user ought to be able to run it, then. > > > Can you enable that account, su to it and try it? > > > > ________________________________ > From: Dave Bolt > Sent: Wednesday, January 3, 2018 2:29 PM > To: pgsql-admin@lists.postgresql.org > Subject: RE: Failed to execute pg_dump > > > 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=20 > 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=20 > 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=20 > 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=20 > conf/config.inc.php : /opt/rh/rh-postgresql96/root/usr/bin/pg_dump).=20 > 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=20 > appears to be the configuration file mentioned in the error message=20 > and I can=E2=80=99t see any obvious issues. > > > > I searched this problem in the mailing list but could not find any=20 > recent results. I did find an older result which said to correct the=20 > 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=20 > http://journyx.com/communication-preferences to unsubscribe.