On Sun, Nov 20, 2011 at 6:21 AM, Marko Kreen <markokr@xxxxxxxxx> wrote:
On Sun, Nov 20, 2011 at 8:32 AM, Phoenix Kiula <phoenix.kiula@xxxxxxxxx> wrote:
> The password I am entering in the terminal is right for sure. I've
> tried it a few times, checked the caps lock, etc. Also, if the log
> carries this "FATAL password authentication failed", why does the
> terminal give the vague error "no working server connection"?
ISTM that either your connect string is bad to the database or you already have too many clients connected to the db. Have you tried:
show max_clients;
select count(1) from pg_stat_activity;
In postgres? Is it possible that there are just too many clients already connected? If not, then it's probably just your connect string ( in pgbouncer.ini) not being quite right. You are using 127.0.0.1 for connecting, is postgres even listening?
netstat -lntp | grep 5432
Good luck.
--Scott
"no working connection" means that client logged into pgbouncer successfully,
but pgbouncer cannot log into server.
Please look into Postrgres log file for details.
If you see no failures there, you have wrong connect string in pgbouncer.ini.
--
marko
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
