Re: [Pgbouncer-general] Again, problem with pgbouncer

I use pgpool but some of the problem you listed are same as I had with pgpool

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.

/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.

Psql: ERROR: No such user:
You have to create the user in postgres, check you users

postgres=# /du

Role name
--------------
testuser

Wolfgang Schwurack
DBA/SA
UEN

-----Original Message-----
From: pgbouncer-general-bounces(at)pgfoundry(dot)org [mailto:pgbouncer-general-bounces(at)pgfoundry(dot)org] On Behalf Of Phoenix Kiula
Sent: Wednesday, October 03, 2012 12:02 PM
To: raghu ram
Cc: pgbouncer-general(at)pgfoundry(dot)org; PG-General Mailing List
Subject: Re: [Pgbouncer-general] [GENERAL] Again, problem with pgbouncer

On Tue, Oct 2, 2012 at 5:27 PM, Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> wrote:
> On Tue, Oct 2, 2012 at 11:29 AM, Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> wrote:
>> On Tue, Oct 2, 2012 at 12:59 AM, Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> wrote:
>>>> Could you please check permission of /var/run/pgbouncer/ directory.
>>>> If pgbouncer directory does not have "postgres" user
>>>> permissions,please assign it and then start the pgbouncer.
>>>
>>>
>>> The /var/run/pgbouncer/ directory has
>>>
>>> chown -R postgres:postgres ..
>>>
>>> The port number everywhere is already 6789.
>>>
>>> What else?
>>
>>
>>
>> And just to be safe, I also added pgbouncer user to postgres group:
>>
>>
>> usermod -a -G postgres pgbouncer
>>
>>
>> Now when I restart the pgbouncess service, it fails. The log has this message:
>>
>>
>> 2012-10-01 23:25:24.004 21037 FATAL
>> Cannot open logfile: '/var/log/pgbouncer.log':
>> Permission denied
>>
>>
>> That file is owned by "postgres:postgres" as indicated in a gazillion
>> threads and documentation online (none of which is comprehensive) but
>> just to be sure I also did this:
>>
>>
>> chown :postgres /var/log/pgbouncer.log
>>
>>
>> Still the same permission error. Seriously, why can't the log message
>> be a little more useful? Why can't it say clearly WHICH USER is
>> looking for permission to the log file? Both "pgbouncer" and
>> "postgres" have permissions (through the group "postgres") on that
>> file. So which is it?
>
>
>
> I made the port number 6389 everywhere. I changed the permissions of
> the pgbouncer.log to:
>
> chown pgbouncer:postgres /var/log/pgbouncer.log
>
> Now at least the service starts. But when I try and connect via the
> pgbouncer ID:
>
> psql -p 6389 -U snipurl_snipurl snipurl
>
> I get this error:
>
> psql: ERROR: No such user: MYSITE_MYSITE
>
> And yet, the authfile has this:
>
> "MYSITE_MYSITE" "<md5 of raw password>"
> "MYSITE_MYSITE" "<raw password>"
> "postgres" "<md5 of string>"
> "MYSITE_pgbouncer" ""
>
>
> The authfile permissions are:
>
> 283377983 -rw-r--r-- 1 pgbouncer postgres 262 Apr 14 11:15
> /var/lib/pgsql/pgbouncer.txt
>
>
> What else?

No response.

Is there anyone who can help me with pgbouncer?

What are the permissions for the authfile, etc?
_______________________________________________
Pgbouncer-general mailing list
Pgbouncer-general(at)pgfoundry(dot)org
http://pgfoundry.org/mailman/listinfo/pgbouncer-general