Re: upgrade causes psql to not work

On 07/26/2012 10:59 AM, BJ Freeman wrote:
> 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
>
> Merlin Moncure sent the following on 7/25/2012 9:42 AM:
>> On Wed, Jul 25, 2012 at 11:42 AM, Merlin Moncure<mmoncure(at)gmail(dot)com>
>> wrote:
>>> On Wed, Jul 25, 2012 at 10:48 AM, BJ Freeman<bjfree(at)free-man(dot)net>
>>> wrote:
>>>> I apologize, psql is running
>>>> if I do
>>>> [root(at)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.
>>>
>>> yeah. probably the issue is that your postgresql.conf is changed.
>>> you probably want to set listen_addresses to 'all' or something like
>>> that.
>>
>> er, '*'

The pg_hba.conf file is half the answer. As Merlin pointed out you need
to check postgresql.conf and see what listen_address is set to. Per his
suggestion if it is not set to '*', this will listen on all IP
addresses. This requires a restart of the server to take effect.

>>
>> merlin
>>
>

--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com