[pgpool-general: 1706] Re: pgpool - issue with md5

[Jayadevan M]

Hi,
Though the password I am supplying is the same and I have not made any changes to the pgpol password, the values in the error message change. Is that how it should be?

2013-05-08 18:23:48 DEBUG: pid 3301: password does not match: frontend:md57a15dc0847a23d5def2b5c7941d8460d pgpool:md5f51e3de26a7f16dbc7ff99b582e882ab
2013-05-08 18:23:51 DEBUG: pid 3317: password does not match: frontend:md54d973dd3805852de6ef2a9d15a46346d pgpool:md554da49b85b7f3f2ebb9bc676182f9d69

Regards,
Jayadevan
-----Original Message-----
From: Tatsuo Ishii [mailto:ishii at postgresql.org]
Sent: Thursday, May 09, 2013 4:29 AM
To: Jayadevan M
Cc: pgpool-general at pgpool.net
Subject: Re: pgpool - issue with md5

> Hi,
> I have been trying to get md5 authentication work with pgpool and keep running into issues (pgpool not picking the right pool_passwd file and so on). Right now, all that seems to be solved, but I am getting a "psql: FATAL:  password authentication failed for user "hbsi"" error. I am attaching the debug output from pgpool. It looks like the password from the frontend and the one in pgpool config keeps changing.
> An error

It seems the cause of the error is apparent: you supplied wrong password.

2013-05-08 18:23:51 DEBUG: pid 3317: password does not match: frontend:md54d973dd3805852de6ef2a9d15a46346d pgpool:md554da49b85b7f3f2ebb9bc676182f9d69

Are you sure to give pgpool same password which is used when you created pool_passwd entry?

> read_password_packet_password: failed to read password packet "p"
> is also present.

This is normal. psql tries to connect to pgpool with no auth and pgpool rejects it with the message, then psql retry with md5 auth.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp


DISCLAIMER: "The information in this e-mail and any attachment is intended only for the person to whom it is addressed and may contain confidential and/or privileged material. If you have received this e-mail in error, kindly contact the sender and destroy all copies of the original communication. IBS makes no warranty, express or implied, nor guarantees the accuracy, adequacy or completeness of the information contained in this email or any attachment and is not liable for any errors, defects, omissions, viruses or for resultant loss or damage, if any, direct or indirect."