On Tue, Sep 21, 2010 at 8:08 PM, Tatsuo Ishii wrote:
> Unfortunately the gdb backtrace does not show enough information
> because of optimization, I guess. Can you take a backtrace with
> optimization disabled binary?
>
> You can obtain this by editing Makefile around line 147.
>
>
I edited conf
> On Tue, Sep 21, 2010 at 10:45 AM, Bryan Murphy wrote:
>
>> I'm sorry, when I went back over to double check my steps I realized I ran
>> the wrong command. I am *still* having the problem. It appears that the
>> MD5 hashes now match, but it's still failing. I have postgres and pgpool
>> insta
On Tue, Sep 21, 2010 at 10:45 AM, Bryan Murphy wrote:
> I'm sorry, when I went back over to double check my steps I realized I ran
> the wrong command. I am *still* having the problem. It appears that the
> MD5 hashes now match, but it's still failing. I have postgres and pgpool
> installed in
On Tue, Sep 21, 2010 at 10:26 AM, Bryan Murphy wrote:
> On Mon, Sep 20, 2010 at 6:23 PM, Tatsuo Ishii wrote:
>
>> I have used PostgreSQL 9.0 + pgpool-II 3.0 and they work fine with md5
>> auth. Your log seems to indicate that the password in pool_passwd and
>> the one in pg_shadow are not identi
On Mon, Sep 20, 2010 at 6:23 PM, Tatsuo Ishii wrote:
> I have used PostgreSQL 9.0 + pgpool-II 3.0 and they work fine with md5
> auth. Your log seems to indicate that the password in pool_passwd and
> the one in pg_shadow are not identical. Can you verify that?
> The query result:
>
> select pass
> I tried the patch file and I still cannot connect. The only other
> difference is that I've already upgraded our images to Postgres 9.0.0 from
> rc1.
>
> Here is the pgpool debug log:
>
> 2010-09-20 19:43:19 DEBUG: pid 1329: I am 1329 accept fd 6
> 2010-09-20 19:43:19 LOG: pid 1329: connecti
On Sun, Sep 19, 2010 at 11:31 PM, Tatsuo Ishii wrote:
> Sorry for delay. I had a trip outside Japan.
>
No problem.
> I found nasty bug with pgpool. Please try attached patches.
>
I tried the patch file and I still cannot connect. The only other
difference is that I've already upgraded our im
Sorry for delay. I had a trip outside Japan.
> Thanks, I should have thought to try that location. :)
>
> I put the pool_passwd file in the expected location (custom build,
> /opt/postgres/etc/pool_passwd and /etc/pool_passwd) and reran my test. I'm
> still having the same connection problem.
I
On Tue, Sep 14, 2010 at 6:55 PM, Tatsuo Ishii wrote:
> Sorry for not enough description about pool_passwd. It's located under
> the same directory as pgpool.conf. So the default is
> /usr/local/etc/pool_passwd.
>
> You need to create /usr/local/etc/pool_passwd if the uid to run pgpool
> server d
> I can't get md5 authentication working with postgres 9rc1 and pgpool-II 3.0.
> I see references to "pool_passwd" in the pgpool documentation, but I see
> nothing indicating *where* this file should exist and how pgpool finds it.
> I've set my accounts up in pcp.conf, however, I do not believe t
I can't get md5 authentication working with postgres 9rc1 and pgpool-II 3.0.
I see references to "pool_passwd" in the pgpool documentation, but I see
nothing indicating *where* this file should exist and how pgpool finds it.
I've set my accounts up in pcp.conf, however, I do not believe this is w
11 matches
Mail list logo
