[pgpool-general: 1410] Re: pcp commands generating EOFError
David Kerr
web at mr-paradox.net
Wed Feb 20 08:14:51 JST 2013
hmm that's interesting, if i switch to 9898 i get
pcp_attach_node -d 100 db02 9898 postgres pass 1
DEBUG: could not connect to "db02"
ConnectionError
i can connect to db02 from command line psql.
On Feb 19, 2013, at 3:03 PM, Lonni J Friedman <netllama at gmail.com> wrote:
> You sure that you're specifying the right port number in that command?
> Typically the pcp_* commands expect the port number of the pgpool
> instance, not the postgres server(s).
>
> On Tue, Feb 19, 2013 at 3:01 PM, David Kerr <web at mr-paradox.net> wrote:
>> Getting the following behavior:
>>
>>> pcp_attach_node -d 100 db02 5432 postgres superpassword 1
>> EOFError
>>
>>
>> (yes -d does nothing)
>>
>>
>> on the postgres side i'm getting:
>> Feb 19 22:54:09 ccdb02 postgres[10660]: [2-1] user=[unknown],db=[unknown],host=192.168.0.38 LOG: invalid length of startup packet
>>
>>
>> I get similar results from all pcp_ programs.
>>
>> Am i missing something from my configuration?
>>
>> Thanks
>
More information about the pgpool-general
mailing list