No subject

Sun Nov 18 18:09:07 JST 2012

password from a new line or if it is passed as an environment variable.

If I set the password, each time, pgppol is showing different md5 values as=
 being received from frontend and pgpool. Does this have any significance?

1) First time
frontend:md5dcfebe668476221778df83b5b42c241b
pgpool:md5b470bbdf80e844f300d96870f14263b9
2) Second time
frontend:md59ff6d16d379b05cb726c64af24d20c8e
pgpool:md5e0b9662db9cda4cac7b91c5c29ceb34f

Does IPV6 have anything to do with this behavior?

Regards,
Jayadevan
-----Original Message-----
From: Tatsuo Ishii [mailto:ishii at postgresql.org]
Sent: Tuesday, May 14, 2013 8:56 AM
To: Jayadevan M
Cc: ishii at postgresql.org; pgpool-general at pgpool.net
Subject: Re: [pgpool-general: 1706] Re: pgpool - issue with md5

Oh ok. My mistake. Because no "pool_passwd" string was in the log, I though=
t it's irrelevant to the issue. Anyway, next time please specify "-s 128" o=
r something like that for strace command. This will show full message of DE=
BUG statements in the log which are trimed by 32 bytes(default).

write(2, "2013-05-13 18:28:43 DEBUG: pid 1"..., 61) =3D 61
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

> Hmmm...That was precisely what I did. There was just one worker process w=
aiting for connection and I attached to that. As soon as I tried psql from =
a client machine, it spit out the messages in the file I sent. Anyway, let =
me try again in another machine and see if I get some output that is more h=
elpful.
> Regards,
> Jayadevan
>
> -----Original Message-----
> From: Tatsuo Ishii [mailto:ishii at postgresql.org]
> Sent: Tuesday, May 14, 2013 4:45 AM
> To: Jayadevan M
> Cc: pgpool-general at pgpool.net
> Subject: Re: [pgpool-general: 1706] Re: pgpool - issue with md5
>
> It seems the trace is not very usefull because it was not against right p=
rocess. Pgpool consists of multiple process. You need to attach one of pgpo=
ol child process you are trying to connect. Unfortunately the process is de=
termined by kernel, and we cannnot predict it. So here is the workaround:
>
> 1) set "num_init_children =3D 1". This will limit the number of process p=
ossbily selected by the kernel to 1. Restart pgpool.
>
> 2)  Look for the process number which looks like by ps:
>
> 5052 pts/6    S      0:00 pgpool: wait for connection request
>
> 3) attach strace to the process and start session from psql
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese: http://www.sraoss.co.jp
>
>> Hi,
>> I tried strace, with pgpool running in daemon mode, with debug option. W=
ould it be possible to have a look at the trace output and identify what is=
 wrong?
>> Regards,
>> Jayadevan
>>
>>
>>>-----Original Message-----
>>>From: Tatsuo Ishii [mailto:ishii at postgresql.org]
>>>Sent: Thursday, May 09, 2013 9:12 AM
>>>To: web at mr-paradox.net
>>>Cc: Jayadevan M; ishii at postgresql.org; pgpool-general at pgpool.net
>>>Subject: Re: [pgpool-general: 1706] Re: pgpool - issue with md5
>>>
>>>> sounds smilier to the problem i had the solution was:
>>>> http://www.pgpool.net/mediawiki/index.php/FAQ
>>>> I cannot use MD5 authentication if start pgpool without -n option. Why=
?
>>>> You must have given -f option as a relative path: i.e. "-f
>>>> pgpool.conf", rather
>>>than full path: i.e. "-f /usr/local/etc/pgpool.conf". Pgpool tries to
>>>locate the full path of pool_passwd (which is neccesary for MD5 auth)
>>>from pgpool.conf path. This is fine with -n option. However if pgpool
>>>starts without -n option, it changes current directory to "/", which
>>>is neccessary processs for daemonizing. As a result, pgpool tries to
>>>open "/pool_passwd", which will not successs.
>>>
>>>Good point. So Jayadevan may look into different pool_passwd file.
>>>strace will reveal the problem...
>>>--
>>>Tatsuo Ishii
>>>SRA OSS, Inc. Japan
>>>English: http://www.sraoss.co.jp/index_en.php
>>>Japanese: http://www.sraoss.co.jp
>>>
>>>> On May 8, 2013, at 8:00 PM, Jayadevan M
>>><jayadevan.maymala at ibsplc.com> wrote:
>>>>
>>>>> 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 s=
o 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 passw=
ord.
>>>>>
>>>>> 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."
>>>>> _______________________________________________
>>>>> pgpool-general mailing list
>>>>> pgpool-general at pgpool.net
>>>>> http://www.pgpool.net/mailman/listinfo/pgpool-general
>>>>>
>>>>
>>
>>
>> DISCLAIMER: "The information in this e-mail and any attachment is intend=
ed 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, kin=
dly contact the sender and destroy all copies of the original communication=
. IBS makes no warranty, express or implied, nor guarantees the accuracy, a=
dequacy or completeness of the information contained in this email or any a=
ttachment and is not liable for any errors, defects, omissions, viruses or =
for resultant loss or damage, if any, direct or indirect."
>
>
> DISCLAIMER: "The information in this e-mail and any attachment is intende=
d 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, kind=
ly contact the sender and destroy all copies of the original communication.=
 IBS makes no warranty, express or implied, nor guarantees the accuracy, ad=
equacy or completeness of the information contained in this email or any at=
tachment and is not liable for any errors, defects, omissions, viruses or f=
or resultant loss or damage, if any, direct or indirect."

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 an=
d/or privileged material. If you have received this e-mail in error, kindly=
 contact the sender and destroy all copies of the original communication. I=
BS makes no warranty, express or implied, nor guarantees the accuracy, adeq=
uacy or completeness of the information contained in this email or any atta=
chment and is not liable for any errors, defects, omissions, viruses or for=
 resultant loss or damage, if any, direct or indirect."