Re: upgrade causes psql to not work - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: upgrade causes psql to not work
Date
Msg-id CADK3HHKj-KJ6Uc2FGz8D1pTs2xuL-jOMA4DyXPqrut4jKF6FxA@mail.gmail.com
Whole thread Raw
In response to upgrade causes psql to not work  (BJ Freeman <bjfree@free-man.net>)
List pgsql-jdbc
Check in postgresql.conf to make sure it is listening on the tcpip port

listen_address='...

netstat -nlp | grep 5432 will tell you for sure

Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca


On Thu, Jul 26, 2012 at 3:40 PM, BJ Freeman <bjfree@free-man.net> wrote:
> did a centos 5.6 server upgrade to PostgreSQL version 8.4.12.
> console:
> [root@main jdbc]# psql -h localhost -U gameserver
> passwordfromentityengine.xml
>
> psql: could not connect to server: Connection refused
>         Is the server running on host "localhost" and accepting
>         TCP/IP connections on port 5432?
>
> I notice there is no localhost and th 127.0.0.1 has /32 added.
> I can not add a localhost to the allowed hosts
>
> psql is running
> if I do
> [root@main jdbc]# psql  -U gameserver
>  passwordfromentityengine.xml
> with out defining the host, it works.
>
> I believe it is using Unix pipes instead of TCP
> I also can manage the psql server through webmin.
>
> I looked on the http://jdbc.postgresql.org/
> and could not find any docs on the jdbc string to use my old one with
> localhost and 127.0.0.1 do not work any more.
> here is the conf
> # "local" is for Unix domain socket connections only
> local all all trust
> # IPv4 local connections:
> host all all 127.0.0.1/32 trust
> # IPv6 local connections:
> host all all ::1/128 trust
> host all all 127.0.0.1 255.255.255.255 trust
> host all all 0.0.0.0 0.0.0.0 trust
>
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
>
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc

pgsql-jdbc by date:

Previous
From: BJ Freeman
Date:
Subject: upgrade causes psql to not work
Next
From: BJ Freeman
Date:
Subject: Re: upgrade causes psql to not work