search

edoburu / docker-pgbouncer

Minimal PgBouncer image that is easy to configure
https://hub.docker.com/r/edoburu/pgbouncer/
MIT License
443 stars 251 forks source link

FATAL pidfile exists, another instance running? #65

Closed zN3utr4l closed 2 months ago

zN3utr4l commented 2 years ago

Docker Version: 4.11.1 PgBouncer Version: 1.17.0 DataBase: Timescale 2.7.2-pg14

This happens every time I turn on the pc and docker starts by itself at start up, while if I do docker run or docker-compose up ... never gives that error of FATAL pidfile exists, another instance running?.

Why this happens?

Log File 2022-08-10 08:30:21.491 UTC [1] LOG kernel file descriptor limit: 1048576 (hard: 1048576); max_client_conn: 150, max expected fd use: 212 2022-08-10 08:30:21.492 UTC [1] LOG listening on 172.20.0.9:6432 2022-08-10 08:30:21.492 UTC [1] LOG listening on 127.0.0.1:6432 2022-08-10 08:30:21.492 UTC [1] WARNING cannot listen on 127.0.0.1:6432: bind(): Address in use 2022-08-10 08:30:21.492 UTC [1] WARNING cannot listen on [::1]:6432: bind(): Address not available 2022-08-10 08:30:21.492 UTC [1] LOG listening on unix:/tmp/.s.PGSQL.6432 2022-08-10 08:30:21.492 UTC [1] LOG process up: PgBouncer 1.17.0, libevent 2.1.12-stable (epoll), adns: udns 0.4, tls: OpenSSL 1.1.1q  5 Jul 2022 2022-08-10 08:30:21.880 UTC [1] LOG C-0x7fa96ffa80c0: DataAnalyser/postgres@172.20.0.1:59670 login attempt: db=DataAnalyser user=postgres tls=no 2022-08-10 08:30:21.902 UTC [1] LOG S-0x7fa96ff520f0: DataAnalyser/postgres@172.20.0.5:5432 new connection to server (from 172.20.0.9:36646) 2022-08-10 08:30:21.909 UTC [1] LOG S-0x7fa96ff520f0: DataAnalyser/postgres@172.20.0.5:5432 SSL established: TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=prime256v1 2022-08-10 08:30:23.440 UTC [1] LOG C-0x7fa96ffa82f0: DataAnalyser/postgres@172.20.0.6:54102 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:24.192 UTC [1] LOG C-0x7fa96ffa8520: DataAnalyser/postgres@172.20.0.8:55784 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:25.810 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55796 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:29.723 UTC [1] LOG C-0x7fa96ffa82f0: DataAnalyser/postgres@172.20.0.6:54102 closing because: client close request (age=6s) 2022-08-10 08:30:30.825 UTC [1] LOG C-0x7fa96ffa82f0: DataAnalyser/postgres@172.20.0.6:54160 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:32.615 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55796 closing because: client close request (age=6s) 2022-08-10 08:30:32.618 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55842 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:32.662 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55842 closing because: client close request (age=0s) 2022-08-10 08:30:32.664 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55844 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:32.756 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55844 closing because: client close request (age=0s) 2022-08-10 08:30:32.759 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55846 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:32.769 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55846 closing because: client close request (age=0s) 2022-08-10 08:30:32.773 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55848 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:32.782 UTC [1] LOG S-0x7fa96ff52320: DataAnalyser/postgres@172.20.0.5:5432 new connection to server (from 172.20.0.9:36728) 2022-08-10 08:30:32.786 UTC [1] LOG S-0x7fa96ff52320: DataAnalyser/postgres@172.20.0.5:5432 SSL established: TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=prime256v1 2022-08-10 08:30:32.811 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55848 closing because: client close request (age=0s) 2022-08-10 08:30:32.813 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55852 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:32.824 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55852 closing because: client close request (age=0s) 2022-08-10 08:30:32.827 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55854 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:32.837 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55854 closing because: client close request (age=0s) 2022-08-10 08:30:32.840 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55856 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:32.899 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55856 closing because: client close request (age=0s) 2022-08-10 08:30:32.902 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55860 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:32.921 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55860 closing because: client close request (age=0s) 2022-08-10 08:30:32.924 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55862 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:32.929 UTC [1] LOG C-0x7fa96ffa8520: DataAnalyser/postgres@172.20.0.8:55784 closing because: client close request (age=8s) 2022-08-10 08:30:33.627 UTC [1] LOG C-0x7fa96ffa82f0: DataAnalyser/postgres@172.20.0.6:54160 closing because: client close request (age=2s) 2022-08-10 08:30:35.384 UTC [1] LOG C-0x7fa96ffa82f0: DataAnalyser/postgres@172.20.0.6:54194 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:36.464 UTC [1] LOG C-0x7fa96ffa8520: DataAnalyser/postgres@172.20.0.8:55878 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:36.498 UTC [1] LOG C-0x7fa96ffa8520: DataAnalyser/postgres@172.20.0.8:55878 closing because: client close request (age=0s) 2022-08-10 08:30:37.940 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55862 closing because: client close request (age=5s) 2022-08-10 08:30:37.943 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55886 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:38.216 UTC [1] LOG C-0x7fa96ffa82f0: DataAnalyser/postgres@172.20.0.6:54194 closing because: client close request (age=2s) 2022-08-10 08:30:39.948 UTC [1] LOG C-0x7fa96ffa82f0: DataAnalyser/postgres@172.20.0.6:54212 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:40.130 UTC [1] LOG C-0x7fa96ffa82f0: DataAnalyser/postgres@172.20.0.6:54212 closing because: client close request (age=0s) 2022-08-10 08:30:41.245 UTC [1] LOG C-0x7fa96ffa82f0: DataAnalyser/postgres@172.20.0.6:54218 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:42.959 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55886 closing because: client close request (age=5s) 2022-08-10 08:30:42.962 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55900 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:44.415 UTC [1] LOG C-0x7fa96ffa82f0: DataAnalyser/postgres@172.20.0.6:54218 closing because: client close request (age=3s) 2022-08-10 08:30:45.940 UTC [1] LOG C-0x7fa96ffa82f0: DataAnalyser/postgres@172.20.0.6:54226 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:47.977 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55900 closing because: client close request (age=5s) 2022-08-10 08:30:47.980 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55908 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:49.122 UTC [1] LOG C-0x7fa96ffa82f0: DataAnalyser/postgres@172.20.0.6:54226 closing because: client close request (age=3s) 2022-08-10 08:30:51.073 UTC [1] LOG C-0x7fa96ffa82f0: DataAnalyser/postgres@172.20.0.6:54240 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:52.994 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55908 closing because: client close request (age=5s) 2022-08-10 08:30:52.997 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55922 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:53.649 UTC [1] LOG C-0x7fa96ffa82f0: DataAnalyser/postgres@172.20.0.6:54240 closing because: client close request (age=2s) 2022-08-10 08:30:55.209 UTC [1] LOG C-0x7fa96ffa82f0: DataAnalyser/postgres@172.20.0.6:54248 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:58.012 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55922 closing because: client close request (age=5s) 2022-08-10 08:30:58.018 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55930 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:30:58.596 UTC [1] LOG C-0x7fa96ffa82f0: DataAnalyser/postgres@172.20.0.6:54248 closing because: client close request (age=3s) 2022-08-10 08:31:00.242 UTC [1] LOG C-0x7fa96ffa82f0: DataAnalyser/postgres@172.20.0.6:54256 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:31:03.043 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55930 closing because: client close request (age=5s) 2022-08-10 08:31:03.046 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55938 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:31:08.063 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55938 closing because: client close request (age=5s) 2022-08-10 08:31:08.065 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55940 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:31:13.081 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55940 closing because: client close request (age=5s) 2022-08-10 08:31:13.084 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55942 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:31:18.094 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55942 closing because: client close request (age=5s) 2022-08-10 08:31:18.097 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55944 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:31:21.485 UTC [1] LOG stats: 7 xacts/s, 7 queries/s, in 4619 B/s, out 3767 B/s, xact 4093 us, query 3823 us, wait 660 us 2022-08-10 08:31:23.109 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55944 closing because: client close request (age=5s) 2022-08-10 08:31:23.111 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55946 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:31:28.124 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55946 closing because: client close request (age=5s) 2022-08-10 08:31:28.126 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55948 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:31:33.142 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55948 closing because: client close request (age=5s) 2022-08-10 08:31:33.145 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55954 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:31:38.161 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55954 closing because: client close request (age=5s) 2022-08-10 08:31:38.164 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55956 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:31:43.178 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55956 closing because: client close request (age=5s) 2022-08-10 08:31:43.182 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55966 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:31:46.497 UTC [1] LOG C-0x7fa96ffa8520: DataAnalyser/postgres@172.20.0.8:56018 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:31:46.549 UTC [1] LOG C-0x7fa96ffa8980: DataAnalyser/postgres@172.20.0.6:54344 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:31:46.563 UTC [1] LOG C-0x7fa96ffa8bb0: DataAnalyser/postgres@172.20.0.8:56022 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:31:46.584 UTC [1] LOG S-0x7fa96ff52550: DataAnalyser/postgres@172.20.0.5:5432 new connection to server (from 172.20.0.9:36902) 2022-08-10 08:31:46.591 UTC [1] LOG S-0x7fa96ff52550: DataAnalyser/postgres@172.20.0.5:5432 SSL established: TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=prime256v1 2022-08-10 08:31:46.607 UTC [1] LOG C-0x7fa96ffa8de0: DataAnalyser/postgres@172.20.0.6:54350 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:31:46.615 UTC [1] LOG C-0x7fa96ffa9010: DataAnalyser/postgres@172.20.0.8:56028 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:31:46.686 UTC [1] LOG C-0x7fa96ffa9240: DataAnalyser/postgres@172.20.0.8:56034 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:31:48.210 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:55966 closing because: client close request (age=5s) 2022-08-10 08:31:48.214 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56044 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:31:50.794 UTC [1] LOG S-0x7fa96ff52780: DataAnalyser/postgres@172.20.0.5:5432 new connection to server (from 172.20.0.9:36950) 2022-08-10 08:31:50.804 UTC [1] LOG S-0x7fa96ff52780: DataAnalyser/postgres@172.20.0.5:5432 SSL established: TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=prime256v1 2022-08-10 08:31:53.233 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56044 closing because: client close request (age=5s) 2022-08-10 08:31:53.238 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56094 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:31:58.268 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56094 closing because: client close request (age=5s) 2022-08-10 08:31:58.270 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56096 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:32:03.283 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56096 closing because: client close request (age=5s) 2022-08-10 08:32:03.285 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56112 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:32:08.300 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56112 closing because: client close request (age=5s) 2022-08-10 08:32:08.303 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56114 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:32:13.319 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56114 closing because: client close request (age=5s) 2022-08-10 08:32:13.321 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56118 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:32:18.333 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56118 closing because: client close request (age=5s) 2022-08-10 08:32:19.660 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56126 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:32:21.485 UTC [1] LOG stats: 2 xacts/s, 2 queries/s, in 2229 B/s, out 336 B/s, xact 13777 us, query 13777 us, wait 447 us 2022-08-10 08:32:24.676 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56126 closing because: client close request (age=5s) 2022-08-10 08:32:24.679 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56128 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:32:29.695 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56128 closing because: client close request (age=5s) 2022-08-10 08:32:29.698 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56158 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:32:34.717 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56158 closing because: client close request (age=5s) 2022-08-10 08:32:34.719 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56168 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:32:39.734 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56168 closing because: client close request (age=5s) 2022-08-10 08:32:39.738 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56184 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:32:44.755 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56184 closing because: client close request (age=5s) 2022-08-10 08:32:44.758 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56206 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:32:49.774 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56206 closing because: client close request (age=5s) 2022-08-10 08:32:49.777 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56226 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:32:54.794 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56226 closing because: client close request (age=5s) 2022-08-10 08:32:54.797 UTC [1] LOG C-0x7fa96ffa8750: DataAnalyser/postgres@172.20.0.8:56242 login attempt: db=DataAnalyser user=postgres tls=TLSv1.2/ECDHE-RSA-AES256-GCM-SHA384/ECDH=X25519 2022-08-10 08:35:48.337 UTC [1] FATAL pidfile exists, another instance running? 2022-08-10 08:35:49.171 UTC [1] FATAL pidfile exists, another instance running? 2022-08-10 08:35:49.844 UTC [1] FATAL pidfile exists, another instance running? 2022-08-10 08:35:50.602 UTC [1] FATAL pidfile exists, another instance running? 2022-08-10 08:35:51.779 UTC [1] FATAL pidfile exists, another instance running? 2022-08-10 08:35:53.691 UTC [1] FATAL pidfile exists, another instance running? 2022-08-10 08:35:57.184 UTC [1] FATAL pidfile exists, another instance running? 2022-08-10 08:36:03.871 UTC [1] FATAL pidfile exists, another instance running? 2022-08-10 08:36:16.930 UTC [1] FATAL pidfile exists, another instance running? 2022-08-10 08:36:42.825 UTC [1] FATAL pidfile exists, another instance running? 2022-08-10 08:37:34.311 UTC [1] FATAL pidfile exists, another instance running? 2022-08-10 08:38:34.663 UTC [1] FATAL pidfile exists, another instance running? 2022-08-10 08:39:34.999 UTC [1] FATAL pidfile exists, another instance running? 2022-08-10 08:40:35.369 UTC [1] FATAL pidfile exists, another instance running? 2022-08-10 08:41:35.687 UTC [1] FATAL pidfile exists, another instance running?

jflambert commented 2 years ago

Could you share a (simplified) docker-compose here

Did this happen with prior versions of pgbouncer?

zN3utr4l commented 2 years ago

This is the first Pgbouncer version i tried

Docker Compose:

version: 3.9

services:
    timescaledb:
        image: timescaledb:2.7.2-pg14
        container_name: timescale
        environment:
            - POSTGRES_PASSWORD=$POSTGRES_PASSWORD
            - POSTGRES_DB=$POSTGRES_DB
            - POSTGRES_HOST_AUTH_METHOD=scram-sha-256
        command: -c config_file=/etc/postgresql.conf
        networks:
            DefaultNet:
                ipv4_address: 172.20.0.5
        volumes:
            - certs:/Certs/Analyser
        ports:
            - 5432:5432

    pgbouncer:
        image: pgbouncer:1.17.0
        restart: always
        networks:
            DefaultNet:
                ipv4_address: 172.20.0.9
        ports:
            - 6432:6432
        volumes:
            - certs:/Certs/Analyser
        depends_on:
            - timescaledb

volumes:
    certs_analyser:
        name: certs

networks:
    DefaultNet:
        name: internal_network
        ipam:
            config:
                - subnet: 172.20.0.0/24

pgbouncer.ini

################## Auto generated ##################
[databases]
TEST= host=172.20.0.5 port=5432 user=postgres

;; Configuration section
[pgbouncer]

;;;
;;; Administrative settings
;;;

logfile = /etc/pgbouncer/pgbouncer.log
pidfile = /var/run/pgbouncer/pgbouncer.pid

;;;
;;; Where to wait for clients
;;;

;; IP address or * which means all IPs
listen_addr = 172.20.0.9, 127.0.0.1, localhost
listen_port = 6432

;; Unix socket is also used for -R.
;; On Debian it should be /var/run/postgresql
;unix_socket_dir = /tmp
;unix_socket_mode = 0777
;unix_socket_group =

;;;
;;; TLS settings for accepting clients
;;;

;; disable, allow, require, verify-ca, verify-full
client_tls_sslmode = allow

;; Path to file that contains trusted CA certs
client_tls_ca_file = /Certs/Analyser/TimeScaleDBCert/testca/cacert.pem

;; Private key and cert to present to clients.
;; Required for accepting TLS connections from clients.
client_tls_key_file = /Certs/Analyser/TimeScaleDBCert/client/key.pem
client_tls_cert_file = /Certs/Analyser/TimeScaleDBCert/client/cert.pem

;; fast, normal, secure, legacy, <ciphersuite string>
client_tls_ciphers = HIGH:MEDIUM:+3DES:!aNULL

;; all, secure, tlsv1.0, tlsv1.1, tlsv1.2, tlsv1.3
client_tls_protocols = tlsv1.2

;; none, auto, legacy
client_tls_dheparams = auto

;; none, auto, <curve name>
client_tls_ecdhcurve = auto

;;;
;;; TLS settings for connecting to backend databases
;;;

;; disable, allow, require, verify-ca, verify-full
server_tls_sslmode = allow

;; Path to that contains trusted CA certs
server_tls_ca_file = /Certs/Analyser/TimeScaleDBCert/testca/cacert.pem

;; Private key and cert to present to backend.
;; Needed only if backend server require client cert.
server_tls_key_file = /Certs/Analyser/TimeScaleDBCert/client/key.pem
server_tls_cert_file = /Certs/Analyser/TimeScaleDBCert/client/cert.pem

;; all, secure, tlsv1.0, tlsv1.1, tlsv1.2, tlsv1.3
server_tls_protocols = tlsv1.2

;; fast, normal, secure, legacy, <ciphersuite string>
server_tls_ciphers = HIGH:MEDIUM:+3DES:!aNULL

;;;
;;; Authentication settings
;;;

;; any, trust, plain, md5, cert, hba, pam, scram-sha-256

auth_type = scram-sha-256
auth_file = /etc/pgbouncer/userlist.txt

;; Path to HBA-style auth config
;auth_hba_file = /etc/pgbouncer/pg_hba.hba

;; Query to use to fetch password from database.  Result
;; must have 2 columns - username and password hash.
; auth_query = SELECT usename, passwd FROM pg_shadow WHERE usename=$1

;;;
;;; Users allowed into database 'pgbouncer'
;;;

;; comma-separated list of users who are allowed to change settings
admin_users = postgres

;; comma-separated list of users who are just allowed to use SHOW command
stats_users = postgres

;;;
;;; Pooler personality questions
;;;

;; When server connection is released back to pool:
;;   session      - after client disconnects (default)
;;   transaction  - after transaction finishes
;;   statement    - after statement finishes
pool_mode = transaction

;; Query for cleaning connection immediately after releasing from
;; client.  No need to put ROLLBACK here, pgbouncer does not reuse
;; connections where transaction is left open.
server_reset_query = DISCARD ALL
;;;
;;; Connection limits
;;;

;; Total number of clients that can connect
max_client_conn = 1000

;; Default pool size.  20 is good number when transaction pooling
;; is in use, in session pooling it needs to be the number of
;; max clients you want to handle at any moment
default_pool_size = 35

;; Minimum number of server connections to keep in pool.
;min_pool_size = 0

; how many additional connection to allow in case of trouble
reserve_pool_size = 10

;; If a clients needs to wait more than this many seconds, use reserve
;; pool.
reserve_pool_timeout = 3

;; Maximum number of server connections for a database
max_db_connections = 150

;;;
;;; Logging
;;;

;; Syslog settings
syslog = 0
syslog_facility = daemon
syslog_ident = pgbouncer

;; log if client connects or server connection is made
log_connections = 1

;; log if and why connection was closed
log_disconnections = 1

;; log error messages pooler sends to clients
log_pooler_errors = 1

;; write aggregated stats into log
log_stats = 1

;; Logging verbosity.  Same as -v switch on command line.
verbose = 0

;;;
;;; Timeouts
;;;

;; Close server connection if its been connected longer.
server_lifetime = 3600

;; Close server connection if its not been used in this time.  Allows
;; to clean unnecessary connections from pool after peak.
server_idle_timeout = 120

;; Cancel connection attempt if server does not answer takes longer.
server_connect_timeout = 15

;; If server login failed (server_connect_timeout or auth failure)
;; then wait this many second before trying again.
server_login_retry = 3

;; Dangerous.  Server connection is closed if query does not return in
;; this time.  Should be used to survive network problems, _not_ as
;; statement_timeout. (default: 0)
query_timeout = 0

;; Dangerous.  Client connection is closed if the query is not
;; assigned to a server in this time.  Should be used to limit the
;; number of queued queries in case of a database or network
;; failure. (default: 120)
query_wait_timeout = 120

;; Dangerous.  Client connection is closed if no activity in this
;; time.  Should be used to survive network problems. (default: 0)
client_idle_timeout = 0

;; Disconnect clients who have not managed to log in after connecting
;; in this many seconds.
client_login_timeout = 60

;; Close connections which are in "IDLE in transaction" state longer
;; than this many seconds.
idle_transaction_timeout = 10000
zN3utr4l commented 2 years ago

Look: https://github.com/pgbouncer/pgbouncer/issues/750

jflambert commented 2 months ago

Hi @zN3utr4l let me know if this is still an issue with v1.23.1-p0 or latest