Re: Pgbouncer and postgres

2018-09-20 Thread Fabio Pardi
I tried to compile 1.8.1 on my (now) up to date Centos 7 and everything went ok. I can run pgbouncer and login to it. this is the relevant part of the diff between config.log files > config.status:1112: lib/usual/config.h is unchanged 4676c4689 < CPPFLAGS='' --- > CPPFLAGS=' -I/usr/local/lib/in

Re: Pgbouncer and postgres

2018-09-19 Thread Adrian Klaver
On 9/19/18 8:39 AM, ncontu1 wrote: So unexpectedly with the rpms, it installed it on a different place and it is working from command line [root@cmd-dev1 pgbouncer]# /bin/pgbouncer /etc/pgbouncer/pgbouncer.ini -u postgres 2018-09-19 15:38:36.081 46322 LOG File descriptor limit: 1024 (H:4096), ma

Re: Pgbouncer and postgres

2018-09-19 Thread ncontu1
So unexpectedly with the rpms, it installed it on a different place and it is working from command line [root@cmd-dev1 pgbouncer]# /bin/pgbouncer /etc/pgbouncer/pgbouncer.ini -u postgres 2018-09-19 15:38:36.081 46322 LOG File descriptor limit: 1024 (H:4096), max_client_conn: 100, max fds possible

Re: Pgbouncer and postgres

2018-09-19 Thread Fabio Pardi
On 19/09/18 15:34, Adrian Klaver wrote: > On 9/19/18 5:40 AM, ncontu wrote: >> Hi Fabio, >> It used to work before, even without installing updates. > > Exactly, the suspicion is that something in the updates changed the behavior > of your system. > Yes, that's the suspicion. Or at least was..

Re: Pgbouncer and postgres

2018-09-19 Thread Adrian Klaver
On 9/19/18 5:40 AM, ncontu wrote: Hi Fabio, It used to work before, even without installing updates. Exactly, the suspicion is that something in the updates changed the behavior of your system. I got two interfaces : private IP and localhost Selinux is disabled. I tried installing it from

Re: Pgbouncer and postgres

2018-09-19 Thread ncontu
Hi Fabio, It used to work before, even without installing updates. I got two interfaces : private IP and localhost Selinux is disabled. I tried installing it from source, from git repo. Can't find the RPM, do you have any link for centos7? I tried both /etc/init.d and command line, same issue. T

Re: Pgbouncer and postgres

2018-09-18 Thread Fabio Pardi
Hi Nicola, I tried to reproduce the problem using pgbouncer 1.8.1 from RPM on CentOS 7 and (an almost equal to) your configuration file but I m not able tobring it to the same error-state. Your problem might be tied either to the way you compiled it, or to some package installed/reconfigured w

Re: Pgbouncer and postgres

2018-09-17 Thread Adrian Klaver
On 9/17/18 9:09 AM, Nicola Contu wrote: 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. Pretty sure you won't as 6543 is controlled by pgbouncer and pgbouncer seems to be failing before it gets around

Re: Pgbouncer and postgres

2018-09-17 Thread Nicola Contu
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:

Re: Pgbouncer and postgres

2018-09-17 Thread Adrian Klaver
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 saf

Re: Pgbouncer and postgres

2018-09-17 Thread Nicola Contu
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 6761

Re: Pgbouncer and postgres

2018-09-17 Thread Adrian Klaver
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-dev

Re: Pgbouncer and postgres

2018-09-17 Thread Adrian Klaver
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 ] PHP WARNING: pg_connect(): Unable to connect to PostgreSQL server: could not connect to server: Connection refused\n\tIs

Re: Pgbouncer and postgres

2018-09-17 Thread Nicola Contu
The log is from pgbouncer. I installed updates after this problem, but they did not resolve anything. I compiled 1.9.0 from source on the same path of the previous one. Then back to 1.8.1 on the same path. I also tried changing the listening port on pgbouncer, but that does not change too much.

Re: Pgbouncer and postgres

2018-09-17 Thread Nicola Contu
[Mon Sep 17 10:24:59.041589 2018] [php7:notice] [pid 63893:tid 140586929567488] [client 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 connection

Re: Pgbouncer and postgres

2018-09-17 Thread Adrian Klaver
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

Re: Pgbouncer and postgres

2018-09-17 Thread Nicola Contu
I'm not aware of any update installed. There were like 600+ updates in fact. These are the logs when connecting via telnet : 2018-09-17 14:18:18.933 65617 NOISE safe_accept(11) = 14 (10.151.2.145:39478 ) 2018-09-17 14:18:18.933 65617 NOISE new fd from accept=14 2018-09-17 14:18:18.933 65617 NOISE

Re: Pgbouncer and postgres

2018-09-17 Thread Adrian Klaver
On 9/17/18 7:05 AM, Nicola Contu wrote: The log is from pgbouncer. I installed updates after this problem, but they did not resolve anything. I was thinking more of updates that where done between the last time it worked and the time it started failing. Along that line, when was the last ti

Re: Pgbouncer and postgres

2018-09-17 Thread Adrian Klaver
On 9/17/18 5:33 AM, Nicola Contu wrote: Hello, I'm trying to get pgbouncer working but I'm getting this error : What is generating the log below? To me it looks like everything is on track until this: 2018-09-17 12:21:48.917 88424 WARNING tune_socket(13) failed: Operation not supported 2