[pgpool-general: 4873] Re: Pgpool2-ERROR: unable to read data from frontend

Kanak Upadhyay kupadhyay at xavient.com
Fri Aug 5 17:48:35 JST 2016


Hi,

Its 3.4.3 (tataraboshi)


Thanks and Regards,
Kanak Upadhyay
Xavient Information Systems


-----Original Message-----
From: Tatsuo Ishii [mailto:ishii at sraoss.co.jp]
Sent: Friday, August 05, 2016 1:49 PM
To: Kanak Upadhyay
Cc: pgpool-general at pgpool.net
Subject: Re: [pgpool-general: 4871] Re: Pgpool2-ERROR: unable to read data from frontend

> Hi Tatsuo,
> Please find the attached configuration file.
>
> And the pgpool2 version I am using is 3.4. In Ubuntu 16 with PostgreSQL 9.5 having 3 nodes one serving as master and other tow serving as slaves.

3.4.x? I need the exact version number.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

> Thanks and Regards,
> Kanak Upadhyay
> Xavient Information Systems
>
>
> -----Original Message-----
> From: Tatsuo Ishii [mailto:ishii at postgresql.org]
> Sent: Friday, August 05, 2016 1:36 PM
> To: Kanak Upadhyay
> Cc: pgpool-general at pgpool.net
> Subject: Re: [pgpool-general: 4865] Pgpool2-ERROR: unable to read data from frontend
>
> Can you share Pgpool-II version, pgpool.conf?
>
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
>
>> But all the connection are from a single machine. The logs itself shows that few connections are fetching records but somehow few are failing.
>>
>> If it would have been on the client side this connection would not have served the request.
>>
>>
>>
>> For instance:
>>
>>
>>
>> HOSTNAME pgpool[8149]:
>>
>>>
>>
>>> 2016-08-04 19:12:51: pid 8195: LOG: DB node id: 1 backend pid: 55023
>>
>>> statement: SELECT * FROM topic WHERE name = 'painters' and ent_id = 1
>>
>>>
>>
>>> Aug 4
>>
>>
>>
>> Thanks and Regards,
>>
>> Kanak Upadhyay
>>
>> Xavient Information Systems
>>
>>
>>
>> -----Original Message-----
>> From: Tatsuo Ishii [mailto:ishii at sraoss.co.jp]
>> Sent: Friday, August 05, 2016 5:01 AM
>> To: Kanak Upadhyay
>> Cc: pgpool-general at pgpool.net
>> Subject: Re: [pgpool-general: 4865] Pgpool2-ERROR: unable to read data from frontend
>>
>>
>>
>> It seems it's client side issue, rather than Pgpool-II issue.  You could verify it by using another client machine or psql on the host Pgpool-II is running on.
>>
>>
>>
>> Best regards,
>>
>> --
>>
>> Tatsuo Ishii
>>
>> SRA OSS, Inc. Japan
>>
>> English: http://www.sraoss.co.jp/index_en.php
>>
>> Japanese:http://www.sraoss.co.jp
>>
>>
>>
>>> Hi,
>>
>>> While making connection the pgool2 is giving error like:
>>
>>> DETAIL: socket read failed with an error "Connection reset by peer"
>>
>>> And the connection are getting rejected.
>>
>>> Is it an issue from pgpool2 end..or is it a connection issue as we are trying to make connection from the windows environment in order to test the load balancing through PGPOOL2.
>>
>>>
>>
>>>
>>
>>> Below are the specified logs:
>>
>>>
>>
>>>
>>
>>> Aug 4
>>
>>>
>>
>>> 19:12:51
>>
>>>
>>
>>> HOSTNAME pgpool[8149]:
>>
>>>
>>
>>> 2016-08-04 19:12:51: pid 8195: LOG: DB node id: 0 backend pid: 10402
>>
>>> statement: BEGIN
>>
>>>
>>
>>> Aug 4
>>
>>>
>>
>>> 19:12:51
>>
>>>
>>
>>> HOSTNAME pgpool[8149]:
>>
>>>
>>
>>> 2016-08-04 19:12:51: pid 8195: LOG: DB node id: 1 backend pid: 55023
>>
>>> statement: BEGIN
>>
>>>
>>
>>> Aug 4
>>
>>>
>>
>>> 19:12:51
>>
>>>
>>
>>> HOSTNAME pgpool[8149]:
>>
>>>
>>
>>> 2016-08-04 19:12:51: pid 8195: LOG: statement: SELECT * FROM topic
>>
>>> WHERE name = 'painters' and ent_id = 1
>>
>>>
>>
>>> Aug 4
>>
>>>
>>
>>> 19:12:51
>>
>>>
>>
>>> HOSTNAME pgpool[8149]:
>>
>>>
>>
>>> 2016-08-04 19:12:51: pid 8195: LOG: DB node id: 0 backend pid: 10402 statement: SELECT count(*) FROM pg_class AS c, pg_namespace AS n WHERE c.relname = 'topic' AND c.relnamespace = n.oid AND n.nspname ~ '^pg_temp_'
>>
>>>
>>
>>> Aug 4
>>
>>>
>>
>>> 19:12:51
>>
>>>
>>
>>> HOSTNAME pgpool[8149]:
>>
>>>
>>
>>> 2016-08-04 19:12:51: pid 8195: LOG: DB node id: 1 backend pid: 55023
>>
>>> statement: SELECT * FROM topic WHERE name = 'painters' and ent_id = 1
>>
>>>
>>
>>> Aug 4
>>
>>>
>>
>>> 19:12:51
>>
>>>
>>
>>> HOSTNAME pgpool[8149]:
>>
>>>
>>
>>> 2016-08-04 19:12:51: pid 8195: ERROR: unable to read data from
>>
>>> frontend
>>
>>>
>>
>>> Aug 4
>>
>>>
>>
>>> 19:12:51
>>
>>>
>>
>>> HOSTNAME pgpool[8149]:
>>
>>>
>>
>>> 2016-08-04 19:12:51: pid 8195: DETAIL: socket read failed with an error "Connection reset by peer"
>>
>>>
>>
>>> Aug 4
>>
>>>
>>
>>> 19:12:51
>>
>>>
>>
>>> HOSTNAME pgpool[8149]:
>>
>>>
>>
>>> 2016-08-04 19:12:51: pid 8195: LOG: statement: ABORT
>>
>>>
>>
>>> Aug 4
>>
>>>
>>
>>> 19:12:51
>>
>>>
>>
>>> HOSTNAME pgpool[8149]:
>>
>>>
>>
>>> 2016-08-04 19:12:51: pid 8195: LOG: DB node id: 1 backend pid: 55023
>>
>>> statement: ABORT
>>
>>>
>>
>>> Aug 4
>>
>>>
>>
>>> 19:12:51
>>
>>>
>>
>>> HOSTNAME pgpool[8149]:
>>
>>>
>>
>>> 2016-08-04 19:12:51: pid 8195: LOG: DB node id: 0 backend pid: 10402
>>
>>> statement: ABORT
>>
>>>
>>
>>> Aug 4
>>
>>>
>>
>>> 19:12:51
>>
>>>
>>
>>> HOSTNAME pgpool[8149]:
>>
>>>
>>
>>> 2016-08-04 19:12:51: pid 8195: LOG: statement: DISCARD ALL
>>
>>>
>>
>>> Aug 4
>>
>>>
>>
>>> 19:12:51
>>
>>>
>>
>>> HOSTNAME pgpool[8149]:
>>
>>>
>>
>>> 2016-08-04 19:12:51: pid 8195: LOG: DB node id: 0 backend pid: 10402
>>
>>> statement: DISCARD ALL
>>
>>>
>>
>>> Aug 4
>>
>>>
>>
>>> 19:12:51
>>
>>>
>>
>>> HOSTNAME pgpool[8149]:
>>
>>>
>>
>>> 2016-08-04 19:12:51: pid 8195: LOG: DB node id: 1 backend pid: 55023
>>
>>> statement: DISCARD ALL
>>
>>>
>>
>>>
>>
>>>
>>
>>> Thanks in advance.
>>
>>>
>>
>>> Thanks and Regards,
>>
>>> Kanak Upadhyay
>>
>>> Xavient Information Systems
>>
>>>
>>
>>> ***DISCLAIMER*** This communication & accompanying documents ("this e-mail") contains confidential and/or privileged information for exclusive use of the individual to whom it is addressed. If you are not the intended recipient, please immediately notify the company & delete this e-mail. Any unauthorized use or disclosure of this e-mail is strictly prohibited. Representations in this e-mail are subject to contract. As an e-mail user please be cautious of the technical & other vulnerabilities of the internet which may result in malicious and/or unauthorized access to / use / alteration of e-mails/e-mail IDs. Thank you.
>>
>> ***DISCLAIMER*** This communication & accompanying documents ("this e-mail") contains confidential and/or privileged information for exclusive use of the individual to whom it is addressed. If you are not the intended recipient, please immediately notify the company & delete this e-mail. Any unauthorized use or disclosure of this e-mail is strictly prohibited. Representations in this e-mail are subject to contract. As an e-mail user please be cautious of the technical & other vulnerabilities of the internet which may result in malicious and/or unauthorized access to / use / alteration of e-mails/e-mail IDs. Thank you.
> ***DISCLAIMER*** This communication & accompanying documents ("this e-mail") contains confidential and/or privileged information for exclusive use of the individual to whom it is addressed. If you are not the intended recipient, please immediately notify the company & delete this e-mail. Any unauthorized use or disclosure of this e-mail is strictly prohibited. Representations in this e-mail are subject to contract. As an e-mail user please be cautious of the technical & other vulnerabilities of the internet which may result in malicious and/or unauthorized access to / use / alteration of e-mails/e-mail IDs. Thank you.
***DISCLAIMER*** This communication & accompanying documents ("this e-mail") contains confidential and/or privileged information for exclusive use of the individual to whom it is addressed. If you are not the intended recipient, please immediately notify the company & delete this e-mail. Any unauthorized use or disclosure of this e-mail is strictly prohibited. Representations in this e-mail are subject to contract. As an e-mail user please be cautious of the technical & other vulnerabilities of the internet which may result in malicious and/or unauthorized access to / use / alteration of e-mails/e-mail IDs. Thank you.


More information about the pgpool-general mailing list