On Thu, Oct 4, 2012 at 2:50 AM, Wolf Schwurack <wolf@uen.org> wrote:
> I use pgpool but some of the problem you listed are same as I had with pgpool
Thanks Wolf, for the thoughts.
> I would not run pgbouner in /var/run/pbbouner. Every time you reboot the
> directory will get deleted. I set my parameter to another directory the would not
> get deleted after a reboot.
OK, but this is not a showstopper here. Right?
> /var/log/pgbouncer.log:
> what is the permission on /var/log? If you don't have write permission on the directory then you cannot write to the
file.
Permissions:
/var/run/pgbouncer --
70058074 drwxr-xr-x 2 pgbouncer postgres 4.0K Oct 2 06:17 pgbouncer/
/var/log --
145686529 drwxr-xr-x 17 root root 4.0K Oct 5 04:29 log/
Please note that whatever the settings, they were working before a
server reboot. What settings do I need to give "/var/log" (currently
root) so the pgbouncer process can write to it? Why are these special
permissions needed-- I mean Apache, MysQL, Nginx etc...all of them can
write to the logs in this log folder.
> Psql: ERROR: No such user:
> You have to create the user in postgres, check you users
>
> postgres=# /du
>
Yes, this user exists in the postgres database.
List of roles
Role name | Attributes | Member of
-----------------+-----------------------------------+-----------
postgres | Superuser, Create role, Create DB | {}
rvadmin | | {}
MYSITE | | {}
MYSITE_MYSITE | Superuser, Create DB | {}
And the authfile also has permissions for "pgbouncer:postgres".
What else?
