From: | Bernard Miville <bmiville(at)iodp-mi-sapporo(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Postgresql, Perl and DBI connect problem |
Date: | 2006-08-22 02:05:21 |
Message-ID: | 44EA6661.5050005@iodp-mi-sapporo.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
I am just trying to connect to a Postgresql DB using a Perl cgi script
from a web page from my own computer on a remote network.
I am using Postgresql 8.1.4 on Fedora Core 5 with a Linux firewall that
allows all traffic.
Postmaster is running with -i and I tried different -h (including *),
right now it is set to 127.0.0.1
In postgresql.conf, I have
listen_addresses='*'
port = 5432.
In pg_hba.conf I have:
local dbname
user md5
host dbname user xxx.xx.xx.x 255.255.255.255 md5
host dbname user 127.0.0.1/32 255.255.255.255 md5
host dbname user ::1/128 255.255.255.255 md5
In the real file, dbname, user and xxx.xx.xx.x are replaced by the
actual value (just in case!!). I also tried all all and trust. For user
there is a password set, and it works locally when I use psql to connect.
I tried different combination (e.g. only 127.0.0.1), like removing the
mask (255.255.255.255) etc. but nothing seems to work.
In the perl cgi script I have:
use DBI;
my $conn =
DBI->connect("DBI:Pg:dbname=dbname;host=127.0.0.1;port=5432;", "user",
"password",{ RaiseError => 1, AutoCommit => 0})|| die "Database
connection not made: $DBI::errstr";;
The error I get is:
DBI connect('dbname=dbname;host=127.0.0.1;port=5432;','user',...) failed: could not create socket: Permission denied
If I remove the host and port from the DBI->connect (which should not be done!) I get this error:
DBI connect('dbname=dbname;','user',...) failed: could not connect to server: Permission denied
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
From another Linux box I am able to remotely connect to the database using:
psql -hxxx.xx.xx.x dbname user
That works fine. It also works locally using psql from the command line, but from the web cgi Perl script it does not connect?
Needless to say, I searched the web and a lot of forums the past 2 days and found a lot of solutions that do not work for my case or
are for Postgresql 7.4 (e.g. tcpip_socket = true does not exist in 8.1, need to use listen_addresses instead).
Any help would be really appreciated.
Thank you,
Bernard
--
_____________________________________________________________________
Bernard Miville
IODP Data Manager
IODP-MI Sapporo Office
CRIS Bldg., Room 05-103, Hokkaido University, N21, W10
Sapporo, Japan 001-0021
Voice: +81 (0)11 738-1072
Fax: +81 (0)11 738-3520
E-Mail: bmiville(at)iodp-mi-sapporo(dot)org
WWW: http://www.iodp.org
SIP: +1747-6068953 (6068953(at)proxy01(dot)sipphone(dot)com)
ENUM: +878107472468937
Skype: mivilleb
_____________________________________________________________________
INTEGRATED OCEAN DRILLING PROGRAM - MANAGEMENT INTERNATIONAL
Washington D.C. & Sapporo
_____________________________________________________________________
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-08-22 03:05:58 | Re: Postgresql, Perl and DBI connect problem |
Previous Message | gao iqiang | 2006-08-22 00:39:00 | unique constraint when updating tables |