[pgpool-general: 5141] Re: md5 authentication failed using port 9999 but succeeds using port 5432

Christophe Le Roux christophe.le.roux at fr.clara.net
Wed Nov 23 17:36:32 JST 2016

Hello Avi,

Didi you see that :

if you want to configure the full authentication (first line of the array), you need to use pg_md5 to generate the md5 hash password for each db user. Look at here : http://www.pgpool.net/docs/pgpool-II-3.5.4/doc/pgpool-en.html#restriction


Christophe LE ROUX
DBA - Claranet

De : pgpool-general-bounces at pgpool.net [mailto:pgpool-general-bounces at pgpool.net] De la part de Avi Weinberg
Envoyé : mardi 22 novembre 2016 17:06
À : pgpool-general at pgpool.net
Objet : [pgpool-general: 5138] md5 authentication failed using port 9999 but succeeds using port 5432

Hi all,

I'm using pgpool 3.5.4.
If I connect with the vip but with the regular port and enter the password it works fine.

[root at postgres_server2 pgpool]# psql -U postgres -h vip_ip -p 5432 -W
Password for user postgres:
psql (9.5.4)

this works!

If I connect the same but this time with pgpool port 9999 and enter the same password I get the following:
[root at postgres_server2 pgpool]# psql -U postgres -h vip_ip -p 9999 -W
Password for user postgres:
psql: ERROR:  md5 authentication failed

How come if I connect directly it works and through pgpool it does not.


IMPORTANT - This email and any attachments is intended for the above named addressee(s), and may contain information which is confidential or privileged. If you are not the intended recipient, please inform the sender immediately and delete this email: you should not copy or use this e-mail for any purpose nor disclose its contents to any person.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20161123/71bb69f8/attachment.html>

More information about the pgpool-general mailing list