Re: could not accept SSL connection: Success

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Carla Iriberri <ciriberri(at)salesforce(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: could not accept SSL connection: Success
Date: 2022-01-19 04:42:00
Message-ID: YeeWmHJnI2dtzPrp@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jan 17, 2022 at 05:05:52PM +0100, Carla Iriberri wrote:
> I saw previous discussions where different errors were logged with the
> "Success"
> message and this was corrected/treated as a bug, but I couldn't find similar
> reports specific to "could not accept SSL connection". Is this a known
> issue or
> case?

Not based my recent mailing list memories, but I may be running short.
The error comes from the backend as you say, where this log would
expect something in saved_errno to feed %m.

And, upstream documentation tells that:
https://www.openssl.org/docs/manmaster/man3/SSL_get_error.html

"On an unexpected EOF, versions before OpenSSL 3.0 returned
SSL_ERROR_SYSCALL, nothing was added to the error stack, and errno was
0. Since OpenSSL 3.0 the returned error is SSL_ERROR_SSL with a
meaningful error on the error stack."

This would mean that relying on %m would be wrong for this case. And
I guess that you are using a version of OpenSSL older than 3.0?
--
Michael

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Shaozhong SHI 2022-01-19 05:10:29 How to schedule running of a script?
Previous Message Allie Crawford 2022-01-19 01:09:53 Re: [Ext:] Re: Stream Replication not working