[pgpool-general: 8438] Re: pgpool failing over on bad queries

[Tatsuo Ishii]

> If I were to disable the health check "health_check_period=0", how does pgpool determine that a backend is down?

failover_on_backend_error
failover_on_backend_shutdown

are enabled, they will detect the backend down and trigger failover.

If they are not enabled, pgpool will try to access backend even if
they are already down.

> Jon Schewe
> 
> Principal Software Systems Technologist
> 
> C: +1 612.263.2718
> 
> O: +1 952.545.5720
> 
> jon.schewe at raytheon.com
> 
> Raytheon BBN
> 
> Raytheon Intelligence & Space
> 
> 5775 Wayzata Blvd. Suite 630
> 
> St. Louis Park, MN 55416
> 
> 
> RTX.com<https://www.rtx.com/> | LinkedIn<https://www.linkedin.com/company/raytheontechnologies> | Twitter<https://twitter.com/raytheontech> | Instagram<https://www.instagram.com/raytheontechnologies>
> 
> ________________________________
> From: pgpool-general <pgpool-general-bounces at pgpool.net> on behalf of Jon SCHEWE <jon.schewe at raytheon.com>
> Sent: Tuesday, September 27, 2022 12:10
> To: Tatsuo Ishii <ishii at sraoss.co.jp>
> Cc: pgpool-general at pgpool.net <pgpool-general at pgpool.net>
> Subject: [External] [pgpool-general: 8427] Re: pgpool failing over on bad queries
> 
> Sorry, I missed that question.
> 
> I have changed the health check user to not require SSL in pg_hba.conf and still see the SSL error.
> 
> This is my pg_hba.conf:
> 
> host replication all 192.1.213.41/32 password
> host db_check db_check 192.1.213.41/32 password
> hostssl all all 192.1.213.41/32 password
> host replication all 192.1.213.42/32 password
> host db_check db_check 192.1.213.42/32 password
> hostssl all all 192.1.213.42/32 password
> host replication all 192.1.213.43/32 password
> host db_check db_check 192.1.213.43/32 password
> hostssl all all 192.1.213.43/32 password
> 
> 
> This is what I see from pgpool with these settings:
> 2022-09-27 12:51:04.962: health_check1 pid 1300221: LOG:  pool_ssl: "SSL_read": "no SSL error reported"
> 2022-09-27 12:51:04.962: health_check1 pid 1300221: LOG:  received degenerate backend request for node_id: 1 from pid [1300221]
> 
> 
> 
> Jon Schewe
> 
> Principal Software Systems Technologist
> 
> C: +1 612.263.2718
> 
> O: +1 952.545.5720
> 
> jon.schewe at raytheon.com
> 
> Raytheon BBN
> 
> Raytheon Intelligence & Space
> 
> 5775 Wayzata Blvd. Suite 630
> 
> St. Louis Park, MN 55416
> 
> 
> RTX.com<https://www.rtx.com/> | LinkedIn<https://www.linkedin.com/company/raytheontechnologies> | Twitter<https://twitter.com/raytheontech> | Instagram<https://www.instagram.com/raytheontechnologies>
> 
> ________________________________
> From: Tatsuo Ishii <ishii at sraoss.co.jp>
> Sent: Monday, September 26, 2022 17:04
> To: Jon SCHEWE <jon.schewe at raytheon.com>
> Cc: pgpool-general at pgpool.net <pgpool-general at pgpool.net>
> Subject: [External] Re: [pgpool-general: 8401] Re: pgpool failing over on bad queries
> 
>> Any updates on this? I have turned of SSL for replication, but I'm still getting errors on the health check. It's happening at least once a week right now.
>>
>>
>> Jon Schewe
> 
> I was waiting for your answer to my question.
> 
>> Have you checked PostgreSQL log so that the health check process does not request SSL connection?
>> You can check it by enabling log_connections in postgresql.conf.
> 
> Best reagards,
> --
> Tatsuo Ishii
> SRA OSS LLC
> English: http://www.sraoss.co.jp/index_en/
> Japanese:http://www.sraoss.co.jp