Обсуждение: upgrade causes psql to not work

Поиск
Список
Период
Сортировка

upgrade causes psql to not work

От
BJ Freeman
Дата:
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

Re: upgrade causes psql to not work

От
Merlin Moncure
Дата:
On Wed, Jul 25, 2012 at 9:57 AM, 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

well, your server is not running (you can confirm this with ps axf).
this is not an issue with pg_hba.conf.

what happens when you try to launch the service manually?

merlin

Re: upgrade causes psql to not work

От
BJ Freeman
Дата:
I apologize, 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.

Merlin Moncure sent the following on 7/25/2012 8:16 AM:
> On Wed, Jul 25, 2012 at 9:57 AM, 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
>
> well, your server is not running (you can confirm this with ps axf).
> this is not an issue with pg_hba.conf.
>
> what happens when you try to launch the service manually?
>
> merlin
>

Re: upgrade causes psql to not work

От
Merlin Moncure
Дата:
On Wed, Jul 25, 2012 at 10:48 AM, BJ Freeman <bjfree@free-man.net> wrote:
> I apologize, 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.

yeah.  probably the issue is that your postgresql.conf is changed.
you probably want to set listen_addresses to 'all' or something like
that.

merlin

Re: upgrade causes psql to not work

От
Merlin Moncure
Дата:
On Wed, Jul 25, 2012 at 11:42 AM, Merlin Moncure <mmoncure@gmail.com> wrote:
> On Wed, Jul 25, 2012 at 10:48 AM, BJ Freeman <bjfree@free-man.net> wrote:
>> I apologize, 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.
>
> 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, '*'

merlin

Re: upgrade causes psql to not work

От
BJ Freeman
Дата:
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@gmail.com>  wrote:
>> On Wed, Jul 25, 2012 at 10:48 AM, BJ Freeman<bjfree@free-man.net>  wrote:
>>> I apologize, 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.
>>
>> 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, '*'
>
> merlin
>

Re: upgrade causes psql to not work

От
Adrian Klaver
Дата:
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@gmail.com>
>> wrote:
>>> On Wed, Jul 25, 2012 at 10:48 AM, BJ Freeman<bjfree@free-man.net>
>>> wrote:
>>>> I apologize, 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.
>>>
>>> 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.klaver@gmail.com