Yes I can connect to port 5432 without any problem. The thing is that I am not seeing anything on the postgres log when connecting to 6543.
Sure, thanks for your help. I will create an issue there. Il giorno lun 17 set 2018 alle ore 18:07 Adrian Klaver < adrian.kla...@aklaver.com> ha scritto: > On 9/17/18 8:59 AM, Nicola Contu wrote: > > Yeah, I replaced the IP of the machine with the word IP_ADDR. > > > > On the pgbouncer log I get this while trying to connect via psql: > > > > 2018-09-17 15:56:49.452 67611 WARNING tune_socket(16) failed: Operation > > not supported > > 2018-09-17 15:56:49.452 67611 NOISE safe_close(16) = 0 > > 2018-09-17 15:56:49.452 67611 NOISE safe_accept(13) = Resource > > temporarily unavailable > > 2018-09-17 15:56:50.728 67611 NOISE safe_accept(13) = 16 (unix:) > > 2018-09-17 15:56:50.729 67611 NOISE new fd from accept=16 > > 2018-09-17 15:56:50.729 67611 WARNING tune_socket(16) failed: Operation > > not supported > > 2018-09-17 15:56:50.729 67611 NOISE safe_close(16) = 0 > > 2018-09-17 15:56:50.729 67611 NOISE safe_accept(13) = Resource > > temporarily unavailable > > 2018-09-17 15:56:56.418 67611 NOISE safe_accept(11) = 16 > > (10.151.2.145:58696 <http://10.151.2.145:58696>) > > 2018-09-17 15:56:56.418 67611 NOISE new fd from accept=16 > > 2018-09-17 15:56:56.418 67611 NOISE safe_accept(11) = Resource > > temporarily unavailable > > Can you connect to the actual database running on port 5432? > > Deciphering the above log is beyond my capabilities. I think it is time > to file an issue here: > > https://github.com/pgbouncer/pgbouncer/issues > > > > -- > Adrian Klaver > adrian.kla...@aklaver.com >
