[pgpool-general: 3536] Re: Amazon EC2 Load Balancer health check kills pgPool node

[Scott Rankin]

Interesting.  At our other data center (not EC2) we get the read_startup_packet error with our load balancer health check.  But with EC2 we get the “unable to read data” and the child process shutdown.

Also we’re using 3.4.1 – I wonder if the behavior is the same with 3.3.1.  I’ll give it a shot.

Thanks all,
Scott

From: James Sewell <james.sewell at lisasoft.com<mailto:james.sewell at lisasoft.com>>
Date: Monday, March 16, 2015 at 8:35 PM
To: Tatsuo Ishii <ishii at postgresql.org<mailto:ishii at postgresql.org>>
Cc: Scott Rankin <srankin at motus.com<mailto:srankin at motus.com>>, "pgpool-general at pgpool.net<mailto:pgpool-general at pgpool.net>" <pgpool-general at pgpool.net<mailto:pgpool-general at pgpool.net>>
Subject: Re: [pgpool-general: 3524] Re: Amazon EC2 Load Balancer health check kills pgPool node

I can see some messages like this also (with the negative packet length), I'm not sure what the difference is - but I'm 99% sure they are all coming from an AWS ELB.

2015-03-16 17:36:25 ERROR: pid 3072: read_startup_packet: incorrect packet length (-565767200)
2015-03-16 17:36:35 ERROR: pid 3072: read_startup_packet: incorrect packet length (0)
2015-03-16 17:36:45 ERROR: pid 3069: read_startup_packet: incorrect packet length (-1746037008)


Cheers,


James Sewell,
PostgreSQL Team Lead / Solutions Architect
______________________________________

[http://www.lisasoft.com/sites/lisasoft/files/u1/logo1.jpg]
Level 2, 50 Queen St, Melbourne VIC 3000

P (+61) 3 8370 8000 Wwww.lisasoft.com  F (+61) 3 8370 8099


On Tue, Mar 17, 2015 at 11:31 AM, Tatsuo Ishii <ishii at postgresql.org<mailto:ishii at postgresql.org>> wrote:
> Hey,
>
> We use the same setup on 3.3.1 (AWS with ELB doing TCP health check), but
> we get these error messages:
>
> 2015-03-16 17:38:05 ERROR: pid 3049: read_startup_packet: incorrect packet
> length (0)
> 2015-03-16 17:38:15 ERROR: pid 3049: read_startup_packet: incorrect packet
> length (0)
> 2015-03-16 17:38:25 ERROR: pid 3049: read_startup_packet: incorrect packet
> length (0)
> 2015-03-16 17:38:35 ERROR: pid 3049: read_startup_packet: incorrect packet
> length (0)
>
> There is no backend crash I can see.

Interesting.

When I connect to pgpool-II localhost with telnet, I see these:

2015-03-17 08:15:50: pid 6436: ERROR:  failed while reading startup packet
2015-03-17 08:15:50: pid 6436: DETAIL:  incorrect packet length (-720903)

This is git HEAD (almost same as 3.4.1).

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



________________________________
The contents of this email are confidential and may be subject to legal or professional privilege and copyright. No representation is made that this email is free of viruses or other defects. If you have received this communication in error, you may not copy or distribute any part of it or otherwise disclose its contents to anyone. Please advise the sender of your incorrect receipt of this correspondence.

This email message contains information that Motus, LLC 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 Motus, LLC, nor should it be used for any purpose other than in the course of any potential or actual business relationship with Motus, LLC. 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20150317/c6f5f4aa/attachment.html>