X-Original-To: pgsql-php-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 7D3779FB395 for ; Mon, 14 Aug 2006 15:06:13 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 67915-08 for ; Mon, 14 Aug 2006 18:06:04 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sydney.mailnetwork.co.uk (server88-208-192-113.live-servers.net [88.208.192.113]) by postgresql.org (Postfix) with ESMTP id F33CE9FB2F5 for ; Mon, 14 Aug 2006 15:06:03 -0300 (ADT) Received: from andyshellam-gw.adsl.newnet.co.uk ([80.175.198.137]:50554 helo=[192.168.1.15]) by sydney.mailnetwork.co.uk with esmtpa (Exim 4.60) (envelope-from ) id 1GCgp7-0003sc-Oq; Mon, 14 Aug 2006 19:06:01 +0100 Message-ID: <44E0BB88.1050500@mailnetwork.co.uk> Date: Mon, 14 Aug 2006 19:06:00 +0100 From: Andy Shellam Reply-To: Andy Shellam Organization: The Mail Network User-Agent: Thunderbird 1.5.0.5 (X11/20060719) MIME-Version: 1.0 To: Fatih Gulec CC: pgsql-php@postgresql.org Subject: Re: DB Error: connect failed References: <2033.193.140.224.60.1155482848.squirrel@cs.hacettepe.edu.tr> <44DF7E5B.6070807@mailnetwork.co.uk> <2220.193.140.224.60.1155545323.squirrel@cs.hacettepe.edu.tr> In-Reply-To: <2220.193.140.224.60.1155545323.squirrel@cs.hacettepe.edu.tr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.133 tagged_above=0 required=5 tests=FORGED_RCVD_HELO, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200608/17 X-Sequence-Number: 3588 Excellent :) No probs, and thanks for posting your solution, it may help someone else out in the future! Andy. Fatih Gulec wrote: > I solve the problem by the help of Andy. > > 1. I change SELinux policy of the /tmp > [root@bulbul /]# chcon -R -h -t httpd_sys_script_rw_t /tmp > 2. I change connection string > old : pgsql://postgres:bbmprens@127.0.0.1/prens > new : pgsql://postgres:bbmprens@unix(/tmp)/prens > > Then it works. > > Thank you so much Andy. > > >> Faith, >> >> I'm guessing one of 2 things is happening here: >> >> - PHP is connecting through the Unix socket in /tmp, and permissions are >> wrong on the /tmp directory for the Apache user >> - Something like TCP wrappers is blocking localhost connections >> >> Try changing the connection host to the machine's ethernet IP address >> instead of 127.0.0.1, this will give you a clue if this is the case. >> You could also examine the PostgreSQL logs - I doubt if it would log >> this error, but it's worth a shot. >> >> Andy. >> >> Fatih Gulec wrote: >> >>> Here is the problem : >>> System : Fedora Core 5 >>> Application server : Apache (comes with Fedora base installation) >>> >>> 1. I could not connect to postgresql in php code whicih uses pear packet >>> DB. Here is the error code : >>> DB Error: connect failed [nativecode=Unable to connect to PostgreSQL >>> server: could not connect to server: Permission denied Is the server >>> running on host "127.0.0.1" and accepting TCP/IP connections on port >>> 5432?] ** pgsql://postgres:bbmprens@127.0.0.1/prens >>> >>> 2. By the way I can connect that db from an other machine which the >>> system >>> is Windows XP and program is default PgAdmin. >>> 2. Alsa I can connect and use from a windows machine with the sama php >>> code that connects to the dbms which works on the Fedora Core 5. >>> 3. The user and password are tested by using pgsql command, in command >>> prompt. >>> >>> Thanks... >>> >>> >>> ---------------------------(end of broadcast)--------------------------- >>> TIP 1: if posting/reading through Usenet, please send an appropriate >>> subscribe-nomail command to majordomo@postgresql.org so that your >>> message can get through to the mailing list cleanly >>> >>> >>> >>> >>> >>> >> ---------------------------(end of broadcast)--------------------------- >> TIP 9: In versions below 8.0, the planner will ignore your desire to >> choose an index scan if your joining column's datatypes do not >> match >> >> > > > !DSPAM:37,44e0388d143291488815628! > > >