On Wed, May 3, 2023 at 9:54 AM Sergey Cherevko
wrote:
> Ubuntu 18.04.6 LTS (GNU/Linux 4.15.0-167-generic x86_64)
>
> OpenSSL 1.1.1 11 Sep 2018
>
> Sometimes i see this in postgres logs
>
So, your system is working normally most of the time? Or is it working
normally all of the time, and you just
00:43:38.570 MSK [27636] [unknown]@[unknown] LOG: could
not accept SSL connection: Success
2023-02-22 00:43:38.570 MSK [27631] [unknown]@[unknown] LOG: could
not accept SSL connection: Success
2023-02-22 00:43:38.570 MSK [27639] [unknown]@[unknown] LOG: could
not accept SSL connection: Success
On Wed, Jan 19, 2022 at 08:06:30PM -0500, Tom Lane wrote:
> Michael Paquier writes:
> > Leaving things in their current state is fine by me. Would it be
> > better to add a note about the business with 3.0 though?
>
> What do you envision saying? "We don't need to do anything here
> for 3.0" do
Michael Paquier writes:
> Leaving things in their current state is fine by me. Would it be
> better to add a note about the business with 3.0 though?
What do you envision saying? "We don't need to do anything here
for 3.0" doesn't seem helpful.
regards, tom lane
On Wed, Jan 19, 2022 at 07:58:43PM -0500, Tom Lane wrote:
> Personally I'm satisfied to leave it as-is, since this issue apparently
> occurs only in a minority of OpenSSL versions, and not the newest.
Leaving things in their current state is fine by me. Would it be
better to add a note about the
Michael Paquier writes:
> I don't think that it makes much sense to leave this unchecked as the
> message is confusing as it stands. Perhaps we could do something like
> the attached by adding a note about OpenSSL 3.0 to revisit this code
> once we unplug support for 1.1.1 and avoiding the errno=
On Thu, Jan 20, 2022 at 09:05:35AM +1300, Thomas Munro wrote:
> Good news, I'm glad they nailed that down. I recall that this
> behaviour was a bit of a moving target in earlier versions:
>
> https://www.postgresql.org/message-id/CAEepm%3D3cc5wYv%3DX4Nzy7VOUkdHBiJs9bpLzqtqJWxdDUp5DiPQ%40mail.gmai
On Thu, Jan 20, 2022 at 12:06 AM Carla Iriberri
wrote:
> On Wed, Jan 19, 2022 at 5:42 AM Michael Paquier wrote:
>> "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 SS
Thanks, Michael, that's it, indeed! I had missed that part of the
OpenSSL docs. These PG instances are running on Ubuntu Focal hosts that come
with OpenSSL 1.1.1.
We had never seen these in the previous Xenial images because those
were using OpenSSL 1.0.2, and from what I've seen the bug was intro
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 know
Hi all,
We've noticed the following connection error logs recently:
sql_error_code = XX000 LOG: could not accept SSL connection: Success
We're seeing this on PostgreSQL databases running on Ubuntu Focal 20.04 with
different PostgreSQL versions (13.5, 13.4, 12.9, 10.19...).
A
11 matches
Mail list logo
