[pgpool-general: 2900] Re: pgpool and SSL connection issues

Tatsuo Ishii ishii at postgresql.org
Wed Jun 4 10:13:25 JST 2014


I've never seen the errors before.
Do you have any idea how to reproduce the the problem?

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

> Hello all,
> 
> We are experiencing intermittent connection issues between pgpool and our postgres database.  We're running pgpool 3.3.3 on CentOS, connecting to PostgreSQL 9.2.2 using SSL.  Normally things are running along smoothly, but every once in a while we'll get the following errors in our logs:
> 
> pgpool[5337]: pool_ssl: SSL_read: ssl handshake failure
> pgpool[4779]: pool_ssl: SSL_read: ssl handshake failure
> pgpool[14436]: pool_read: read failed (Success)
> pgpool[104]: pool_ssl: SSL_read: ssl handshake failure
> pgpool[16848]: pool_ssl: SSL_read: ssl handshake failure
> pgpool[16848]: pool_read: read failed (Success)
> pgpool[5113]: pool_read: read failed (Success)
> pgpool[16964]: SSL_write error: 5
> pgpool[14438]: pool_read: read failed (Success)
> pgpool[16932]: pool_ssl: SSL_read: ssl handshake failure
> pgpool[16879]: ProcessFrontendResponse: failed to read kind from frontend. frontend abnormally exited
> pgpool[16792]: ProcessFrontendResponse: failed to read kind from frontend. frontend abnormally exited
> pgpool[16901]: ProcessFrontendResponse: failed to read kind from frontend. frontend abnormally exited
> pgpool[17018]: ProcessFrontendResponse: failed to read kind from frontend. frontend abnormally exited
> pgpool[16920]: ProcessFrontendResponse: failed to read kind from frontend. frontend abnormally exited
> pgpool[16970]: ProcessFrontendResponse: failed to read kind from frontend. frontend abnormally exited
> pgpool[16889]: ProcessFrontendResponse: failed to read kind from frontend. frontend abnormally exited
> pgpool[16995]: ProcessFrontendResponse: failed to read kind from frontend. frontend abnormally exited
> pgpool[5395]: pool_read: read failed (Success)
> pgpool[14453]: ProcessFrontendResponse: failed to read kind from frontend. frontend abnormally exited
> pgpool[218]: pool_read: read failed (Success)
> pgpool[10905]: pool_ssl: SSL_read: ssl handshake failure
> pgpool[17004]: ProcessFrontendResponse: failed to read kind from frontend. frontend abnormally exited
> pgpool[10901]: ProcessFrontendResponse: failed to read kind from frontend. frontend abnormally exited
> pgpool[5442]: pool_read: read failed (Success)
> pgpool[16936]: ProcessFrontendResponse: failed to read kind from frontend. frontend abnormally exited
> pgpool[10788]: pool_ssl: SSL_read: ssl handshake failure
> 
> This will go on for a few minutes and then (usually) go away.  During this time other (non-pooled) connections to the database continue to work.  Has anybody seen something like this, or have any additional tips that we could use to debug this?
> 
> Thanks,
> Scott
> 
> Scott Rankin
> Corporate Reimbursement Services, Inc.
> Phone: 617-467-1931
> Email: srankin at crsinc.com<mailto:srankin at crsinc.com>
> 
> This email message contains information that Corporate Reimbursement Services, Inc. considers confidential and/or proprietary, or may later designate as confidential and proprietary. It is intended only for use of the individual or entity named above and should not be forwarded to any other persons or entities without the express consent of Corporate Reimbursement Services, Inc., nor should it be used for any purpose other than in the course of any potential or actual business relationship with Corporate Reimbursement Services, Inc. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify sender immediately and destroy the original message.
> 
> Internal Revenue Service regulations require that certain types of written advice include a disclaimer. To the extent the preceding message contains advice relating to a Federal tax issue, unless expressly stated otherwise the advice is not intended or written to be used, and it cannot be used by the recipient or any other taxpayer, for the purpose of avoiding Federal tax penalties, and was not written to support the promotion or marketing of any transaction or matter discussed herein.


More information about the pgpool-general mailing list