pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Holger Jakobs <holger@jakobs.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: unknown postgres ssl error "could not accept SSL connection: Success" and timeout
Date: Thu, 4 May 2023 10:16:28 +0200
Message-ID: <edd088e2-bae2-d7eb-cbf2-f8d2e1f4f5b0@jakobs.com> (raw)
In-Reply-To: <CAECa+gbN4kwke020Wp1PGDYXFpqjryhOoWtSXv5k5eN4pSL=9w@mail.gmail.com>
References: <CAECa+gbN4kwke020Wp1PGDYXFpqjryhOoWtSXv5k5eN4pSL=9w@mail.gmail.com>

Am 03.05.23 um 15:55 schrieb Sergey Cherevko:
> I already send this to general list, may be i need to post in admin
>
> 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
>
> Found some similar threads, but not sure
>
> https://github.com/modoboa/modoboa/issues/1702
>
> https://postgrespro.com/list/thread-id/2585389
>
> How i can to debug this?
>
> |2023-02-22 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 2023-02-22 00:43:38.570 MSK [27642] 
> [unknown]@[unknown] LOG:  could not accept SSL connection: Success 
> 2023-02-22 00:43:38.570 MSK [27643] [unknown]@[unknown] LOG:  could 
> not accept SSL connection: Success 2023-02-22 00:43:38.570 MSK [27627] 
> [unknown]@[unknown] LOG:  could not accept SSL connection: Connection 
> reset by peer |
> CRITICAL
> PDOException
> SQLSTATE[08006] [7] timeout expired
> PDOException
> /var/log/web/hub2.log
> Feb 21, 2023 @ 23:43:38.001
> CRITICAL
> PDOException
> SQLSTATE[08006] [7] timeout expired
> PDOException
> /var/log/web/hub2.log
> Feb 21, 2023 @ 23:43:38.001
> CRITICAL
> PDOException
> SQLSTATE[08006] [7] timeout expired
> PDOException
> /var/log/web/hub2.log
>
> here is my postgres config
>
> |cat /etc/postgresql/12/main/postgresql.conf data_directory = 
> '/var/lib/postgresql/12/main' hba_file = 
> '/etc/postgresql/12/main/pg_hba.conf' ident_file = 
> '/etc/postgresql/12/main/pg_ident.conf' external_pid_file = 
> '/var/run/postgresql/12-main.pid' listen_addresses = '*' port = 5432 
> max_connections = 10000 unix_socket_directories = 
> '/var/run/postgresql' ssl = on ssl_cert_file = 
> '/etc/ssl/certs/ssl-cert-snakeoil.pem' ssl_key_file = 
> '/etc/ssl/private/ssl-cert-snakeoil.key' shared_buffers = 4GB 
> temp_buffers = 8MB work_mem = 128MB maintenance_work_mem = 128MB 
> dynamic_shared_memory_type = posix bgwriter_lru_maxpages = 0 
> effective_io_concurrency = 3 wal_level = hot_standby 
> checkpoint_completion_target = 0.9 archive_mode = on archive_command = 
> '/bin/true' archive_timeout = 300 max_standby_archive_delay = 21600 
> max_standby_streaming_delay = 21600|
> ||
> I should to update my openssl to see real error? How can i do that if i use ubuntu 18.04?

I am not sure what causes the problem, but some hints anyway:

|max_connections = 10000 |

|seems very high to me. In case you really have so many clients, 
consider using a connection pooler.|
||
||

|archive_mode = on archive_command = '/bin/true' archive_timeout = 300 |

||

This is awkward. If you want archiving, use a command which does 
archiving, not /bin/true, which does nothing. Otherwise, turn archiving 
off and leave archive_command empty.

Kind Regards,

Holger


-- 
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012



Attachments:

  [application/pgp-signature] OpenPGP_signature (202B, ../edd088e2-bae2-d7eb-cbf2-f8d2e1f4f5b0@jakobs.com/3-OpenPGP_signature)
  download

view thread (6+ messages)  latest in thread

Message-ID: <edd088e2-bae2-d7eb-cbf2-f8d2e1f4f5b0@jakobs.com>
Permalink:  ../edd088e2-bae2-d7eb-cbf2-f8d2e1f4f5b0@jakobs.com/
Also on:    postgresql.org/message-id/edd088e2-bae2-d7eb-cbf2-f8d2e1f4f5b0@jakobs.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: holger@jakobs.com, pgsql-admin@lists.postgresql.org
  Subject: Re: unknown postgres ssl error "could not accept SSL connection: Success" and timeout
  In-Reply-To: <edd088e2-bae2-d7eb-cbf2-f8d2e1f4f5b0@jakobs.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox