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 ) 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 Il giorno lun 17 set 2018 alle ore 17:46 Adrian Klaver < adrian.kla...@aklaver.com> ha scritto: > On 9/17/18 8:39 AM, Nicola Contu wrote: > Please reply to list also. > Ccing list. > > > No wait, IP_ADDR has been modified by me, but there is the IP of the > > machine 10.151.x. > > To be clear in your posts you are replacing the actual IP with IP_ADDR, > correct? > > > > > > > Here is the psql command . > > > > [root@cmd-dev1 ~]# psql -U ncontu -p 6543 cmd3dev > > psql: server closed the connection unexpectedly > > This probably means the server terminated abnormally > > before or while processing the request. > > So what does the pgbouncer log show when you do above? > > > > > > > > > > > Il giorno lun 17 set 2018 alle ore 17:35 Adrian Klaver > > <adrian.kla...@aklaver.com <mailto:adrian.kla...@aklaver.com>> ha > scritto: > > > > On 9/17/18 7:26 AM, Nicola Contu wrote: > > > [Mon Sep 17 10:24:59.041589 2018] [php7:notice] [pid 63893:tid > > > 140586929567488] [client 10.160.41.3:51764 > > <http://10.160.41.3:51764> <http://10.160.41.3:51764>] > > > PHP WARNING: pg_connect(): Unable to connect to PostgreSQL > > server: could > > > not connect to server: Connection refused\n\tIs the server > > running on > > > host "IP_ADDR" and accepting\n\tTCP/IP connections on > port > > > 6543? in /home/cmd3/adodb5/drivers/adodb-postgres64.inc.php on > > line 727 > > > > To me it looks like IP_ADDR is not resolving to a host. > > > > In your pgbouncer.ini I see: > > > > DB_NAME = host=IP_ADDD port=5432 dbname=DB_NAME auth_user=pgbouncer > > pool_size=120 > > > > but the error is about connecting to port 6543 which is your > pgbouncer > > 'server'. > > > > Are you sure your connection string is pointing at the correct thing? > > > > > > > > So basically the same I get when connecting via psql on port 6543 > > > > What is the full psql command? > > > > > > > > Il giorno lun 17 set 2018 alle ore 16:23 Adrian Klaver > > > <adrian.kla...@aklaver.com <mailto:adrian.kla...@aklaver.com> > > <mailto:adrian.kla...@aklaver.com > > <mailto:adrian.kla...@aklaver.com>>> ha scritto: > > > > > > On 9/17/18 7:19 AM, Nicola Contu wrote: > > > > I'm not aware of any update installed. There were like 600+ > > > updates in fact. > > > > > > > > These are the logs when connecting via telnet : > > > > > > How about those from when Apache tries to connect and > > pgbouncer crashes? > > > > > > > Connection closed by foreign host. > > > > > > > > > -- > > > Adrian Klaver > > > adrian.kla...@aklaver.com <mailto:adrian.kla...@aklaver.com> > > <mailto:adrian.kla...@aklaver.com <mailto:adrian.kla...@aklaver.com > >> > > > > > > > > > -- > > Adrian Klaver > > adrian.kla...@aklaver.com <mailto:adrian.kla...@aklaver.com> > > > > > -- > Adrian Klaver > adrian.kla...@aklaver.com >
