[pgpool-general: 3690] Re: DETAIL: invalid backend response. Response does not replied with "R"

Megan . nagemnna at gmail.com
Fri May 8 02:31:13 JST 2015


I changed it to notice, restarted postgres, restarted pgpool and I get
the same error.  I see nothing in the postgres log for the attempt.
I have selinux off and iptables off just to eliminate those as the

Thanks!

On Thu, May 7, 2015 at 10:40 AM, Muhammad Usama <m.usama at gmail.com> wrote:
>
>
> On Thu, May 7, 2015 at 7:30 PM, Megan . <nagemnna at gmail.com> wrote:
>>
>> Thanks for your reply.
>>
>> I have it set to log:  client_min_messages = log
>>
> client_min_messages = log should be fine, but still to be sure, can you
> please try restoring it to default value (i.e client_min_messages =  notice)
> and check if it works.
> And are you getting any authentication failure messages in postgresql server
> log?
>
> Thanks and regards
> Muhammad Usama
>
>>
>> Is this an issue?
>>
>> Thanks.
>>
>> On Thu, May 7, 2015 at 8:48 AM, Muhammad Usama <m.usama at gmail.com> wrote:
>> > Hi
>> >
>> > Can you check the value of PostgreSQL's client_min_messages
>> > configuration in
>> > postgresql.conf.
>> > Looking at the code it appears that if client_min_messages in PG's
>> > configuration is set to some level of DEBUG.., it could cause this
>> > issue.
>> >
>> > Thanks
>> > Best regards
>> > Muhammad Usama
>> >
>> > On Wed, May 6, 2015 at 9:59 PM, Megan . <nagemnna at gmail.com> wrote:
>> >>
>> >> Good Day all,
>> >>
>> >> I am having some problems with pgpool authentication.  I just setup
>> >> this db server.
>> >>
>> >> Centos 6.6
>> >> pgpool-II-93-3.4.1-1.rhel6.x86_64
>> >> postgresql93-server-9.3.6-1PGDG.rhel6.x86_64
>> >>
>> >> I am running pgpool in mater/slave mode with postgres running
>> >> streaming replication
>> >>
>> >>
>> >> When trying to connect into pgpool i get the below error:
>> >>
>> >> [user at mgmt1 ~]$ psql -h x.x.x.175 -p 9999 -U dbuser dbuser
>> >> Password for user dbuser:
>> >> psql: ERROR:  authentication failed
>> >> DETAIL:  invalid backend response. Response does not replied with "R"
>> >>
>> >> [user at mgmt1 ~]$ hostname -i
>> >> x.x.x.173
>> >>
>> >>
>> >> .175 address is the floating IP address configured for pgpool.
>> >>
>> >> I made sure that I had the md5 password the same in the DB as in the
>> >> pool_passwd file.  I made sure both hba files were using md5. Below
>> >> are my config files.  Any suggestions on how to figure out what is
>> >> wrong are greatly appreciated.
>> >>
>> >>
>> >>
>> >>
>> >> My pool_hba.conf
>> >>
>> >> # IPv4 local connections:
>> >> host    all         all         127.0.0.1/32          trust
>> >> host    postgres        postgres        x.x.x.177/32        trust
>> >> host    postgres        postgres        x.x.x.176/32        trust
>> >> host    postgres        postgres        x.x.x.175/32        trust
>> >> host    postgres          postgres        x.x.x.173/32        trust
>> >> #mgmt1-pro
>> >> host dbuser          dbuser         x.x.x.173/32          md5
>> >> #admin1-prod
>> >> host    dbuser             dbuser             x.x.x.171/32         md5
>> >> host dbuser          dbuser          x.x.x.175/32          md5
>> >>
>> >>
>> >> cat pool_passwd
>> >> dbuser:md5112ee5fd83c53bed5e51897dcfb1e626
>> >>
>> >>
>> >> [root at db1 data]# cat pg_hba.conf
>> >> # TYPE  DATABASE        USER            ADDRESS                 METHOD
>> >> ##local postgres user
>> >> local   all             postgres
>> >> trust
>> >> ##for pgpool
>> >> host    postgres        health_check        x.x.x.176/32        trust
>> >> host    postgres        health_check        x.x.x.177/32        trust
>> >> #pgpool failover
>> >> local    postgres        pgp_fail                trust
>> >> local    postgres        pgp_fail               trust
>> >> host    all             all             127.0.0.1/32            md5
>> >> ##replication user
>> >> host    replication     repli_user     x.x.x.177/32        md5
>> >> host    replication     repli_user     x.x.x.176/32        md5
>> >> #other db host
>> >> host    postgres        postgres        x.x.x.177/32        trust
>> >> host    postgres        postgres        x.x.x.176/32        trust
>> >> #local   dbuser     dbuser                             md5
>> >> ##build host for non pgpool connection
>> >> host    dbuser     dbuser     x.x.x.28/32     md5
>> >> ##for dbuser through pgpool
>> >> host   dbuser              dbuser          x.x.x.177/32        md5
>> >> host   dbuser              dbuser          x.x.x.176/32        md5
>> >> host    dbuser             dbuser             x.x.x.175/32       md5
>> >> host postgres postgres x.x.x.173/32 md5
>> >> host dbuser dbuser x.x.x.173/32        md5
>> >>
>> >>
>> >>
>> >> postgres=# select passwd from pg_shadow where usename = 'dbuser';
>> >>                passwd
>> >> -------------------------------------
>> >>  md5112ee5fd83c53bed5e51897dcfb1e626
>> >> (1 row)
>> >>
>> >>
>> >>
>> >>
>> >> Part from the pgpool debug:
>> >>
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DEBUG:  I am 2399
>> >> accept fd 8
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:LOG:  new
>> >> connection received
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DETAIL:
>> >> connecting host=mgmt1.example.com port=39541
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DEBUG:  reading
>> >> startup packet
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DETAIL:  Protocol
>> >> Major: 1234 Minor: 5679 database:  user:
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DEBUG:  selecting
>> >> backend connection
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DETAIL:
>> >> SSLRequest from client
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DEBUG:  reading
>> >> startup packet
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DETAIL:  Protocol
>> >> Major: 3 Minor: 0 database: dbuser user: dbuser
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DEBUG:  creating
>> >> new connection to backend
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DETAIL:
>> >> connecting 0 backend
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DEBUG:  creating
>> >> new connection to backend
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DETAIL:  skipping
>> >> backend slot 0 because backend_status = 3
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DEBUG:  creating
>> >> new connection to backend
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DETAIL:
>> >> connecting 1 backend
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DEBUG:  reading
>> >> message length
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DETAIL:  slot: 1
>> >> length: 12
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DEBUG:
>> >> authentication backend
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DETAIL:  auth
>> >> kind:5
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DEBUG:
>> >> authentication backend
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DETAIL:  trying
>> >> md5 authentication
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DEBUG:  performing
>> >> md5 authentication
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DETAIL:  DB node
>> >> id: 1 salt: ffffffa64ffffff8432
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:ERROR:
>> >> authentication failed
>> >> 2015-05-06 16:56:49: pid 2399: user [No Connection]:DETAIL:  invalid
>> >> backend response. Response does not replied with "R"
>> >> _______________________________________________
>> >> pgpool-general mailing list
>> >> pgpool-general at pgpool.net
>> >> http://www.pgpool.net/mailman/listinfo/pgpool-general
>> >
>> >
>
>


More information about the pgpool-general mailing list