From: | Carol Walter <walterc(at)indiana(dot)edu> |
---|---|
To: | |
Cc: | <donghe(at)caltech(dot)edu>, "Andy Shellam" <andy-lists(at)networkmail(dot)eu>, <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: PHP cann't access to postgres databse |
Date: | 2009-06-26 17:24:34 |
Message-ID: | B09B5FB5-A0E5-4085-BD9C-45C150385BF3@indiana.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I think that permissions on the parent directories can result in this
error.
Carol
On Jun 26, 2009, at 1:07 PM, Kevin Grittner wrote:
> Andy Shellam <andy-lists(at)networkmail(dot)eu> wrote:
>
>> donghe(at)caltech(dot)edu wrote:
>>> Unable to connect to PostgreSQL server:
>>> could not connect to server: Permission denied
>>> Is the server running on host "localhost" and accepting
>>> TCP/IP connections on port 5432? "
>
>> Because the error is "Permission denied", I'm guessing it's
>> permissions on the /tmp/.s.PGSQL.5432 socket that will need
>> checking?
>
> If it was trying to get that sort of connection, rather than TCP/IP,
> the message would be different. Something like:
>
> # could not connect to server: No such file or directory
> # Is the server running locally and accepting
> # connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
>
> You do have a point on the "Permission denied", though. If the
> problem was where I was suggesting, it would probably say "Connection
> refused". Perhaps some OS security restriction is in play here.
>
> -Kevin
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Shellam | 2009-06-26 17:27:56 | Re: PHP cann't access to postgres databse |
Previous Message | donghe | 2009-06-26 17:24:23 | Re: PHP cann't access to postgres databse |