Re: Pgbouncer and postgres

No the old one is stopped, so not sure why it says the port is in use.

Attached the config.log

Thanks

Il giorno mer 19 set 2018 alle ore 18:02 Adrian Klaver <
adrian(dot)klaver(at)aklaver(dot)com> ha scritto:

> 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(at)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: 230
> > 2018-09-19 15:38:36.082 46322 LOG Stale pidfile, removing
> > 2018-09-19 15:38:36.082 46322 LOG listening on 0.0.0.0:6543
> > 2018-09-19 15:38:36.082 46322 LOG listening on ::/6543
> > 2018-09-19 15:38:36.083 46322 WARNING Cannot listen on
> > unix:/tmp/.s.PGSQL.6543: bind(): Address already in use
>
> Is the compiled version still running?
>
> Or is something else sitting on the 6543 socket?
>
> > 2018-09-19 15:38:36.083 46322 LOG process up: pgbouncer 1.8.1, libevent
> > 2.0.21-stable (epoll), adns: c-ares 1.10.0, tls: OpenSSL 1.0.2k-fips 26
> Jan
> > 2017
> >
> > [root(at)cmd-dev1 ~]# psql -U ncontu -p 6543 cmd3dev -h IP_ADD
> > Password for user ncontu:
> > psql (10.5)
> > Type "help" for help.
> >
> > cmd3dev=# \q
> >
> >
> > So at this point... I don't really know why compiled from source it does
> not
> > work.
>
> Not sure.
>
> For those that might know it would help to provide the complete
> ./configure used and the config.log(or equivalent)
>
> >
> >
> >
> > --
> > Sent from:
> http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
> >
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>