X-Original-To: pgsql-php-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 759A852DC4 for ; Mon, 15 Aug 2005 11:30:16 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 15561-09 for ; Mon, 15 Aug 2005 14:30:14 +0000 (GMT) Received: from mout.perfora.net (mout.perfora.net [217.160.230.40]) by svr1.postgresql.org (Postfix) with ESMTP id BE38B52C2B for ; Mon, 15 Aug 2005 11:30:12 -0300 (ADT) Received: from ool-45782123.dyn.optonline.net [69.120.33.35] (helo=[192.168.2.18]) by mrelay.perfora.net with ESMTP (Nemesis), id 0MKoyl-1E4fyf18Y4-0007ex; Mon, 15 Aug 2005 10:30:13 -0400 In-Reply-To: <923c3c1405081410326a1c2880@mail.gmail.com> References: <923c3c1405081410326a1c2880@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Cc: pgsql-php@postgresql.org From: Matthew Terenzio Subject: Re: Problem about connecting PostgreSQL through TCP/IP Date: Mon, 15 Aug 2005 10:30:12 -0400 To: Hui Chen X-Mailer: Apple Mail (2.622) X-Provags-ID: perfora.net abuse@perfora.net login:55dcc513cc7db400396c2523adeeb8ca X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.153 required=5 tests=[AWL=0.153] X-Spam-Level: X-Archive-Number: 200508/24 X-Sequence-Number: 3236 > > restart posgresql by > /sbin/service postgresql restart > The server was restarted OK. > I usually use pg_ctl to start. With it and other methods of starting postgres you have to include the -i flag to get it to listen over TCP/IP perhaps your method of restarting needs this flag as well? > The PHP script used to connect database is as follows, > $conn = pg_connect("host=localhost port=5432 dbname=foodb user=foo > password=foo") or die ("Can not connect to postgres"); > $result=pg_exec("SELECT * FROM footbl"); > $fetch = pg_fetch_row($result); > print ""; > print $fetch[0]; > print ""; > > pg_close($conn); // Close this connection > ?> > > Assume this PHP script is named as "connectdb.php", then on > commandline, when I run the following, > php connectedb.php > I see correct results, e.g., > foo > > On commandline again, I used the following to connect database, > psql -d foodb -h localhost -p 5432 -U foo > Password: ************ > Welcome to psql 8.0.3, the PostgreSQL interactive terminal. > > Type: \copyright for distribution terms > \h for help with SQL commands > \? for help with psql commands > \g or terminate with semicolon to execute query > \q to quit > > foodb=> > > It is OK. Then I disabled "iptables" temporarily for testing purpose by > /sbin/service iptables stop > Flushing firewall rules: [ OK ] > Setting chains to policy ACCEPT: filter [ OK ] > Unloading iptables modules: [ OK ] > > On localhost, I tried this command, > telnet localhost 5432 > after hit "enters", telnet exited. I checked postgresql_%S.log and see > "LOG: invalid length of startup packet" > which means postgresql server indeed saw the telnet connection. > > I tried this on any of my other machines in the LAN, I observed the > same thing. > > In summary, it seemed the postgresql allowed TCP/IP connection, and > worked well. However, when I ran the PHP script through web browser, I > did not get connection. Instead, in Apache web server's error_log, I > see > [client 192.168.1.10] PHP Warning: pg_connect() [ href='function.pg-connect'>function.pg-connect]: Unable to connect > to PostgreSQL server: could not connect to server: Permission > denied\n\tIs the server running on host "localhost" and > accepting\n\tTCP/IP connections on port 5432? in /foo/connectdb.php on > line 2 > > Interestingly, when I checked the log file for postgresql again, it > did not have anything for this connection failure. It seemed the > connection did not send to the database server at all. However, > 1) I disabled firewall > 2) I can telnet the ports > 3) I can run the script from commandline > > What could go wrong? > > Thanks a lot for your reading this lengthy email. Waiting for your > help! > > Gray > > ---------------------------(end of > broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org >