pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
problem with an account name 'replication' for streaming replication
5+ messages / 3 participants
[nested] [flat]

* problem with an account name 'replication' for streaming replication
@ 2011-03-30 18:37 Uwe Bartels <uwe.bartels@gmail.com>
  2011-03-30 20:43 ` Re: problem with an account name 'replication' for streaming replication raghu ram <raghuchennuru@gmail.com>
  2011-03-31 02:53 ` Re: problem with an account name 'replication' for streaming replication Fujii Masao <masao.fujii@gmail.com>
  0 siblings, 2 replies; 5+ messages in thread

From: Uwe Bartels @ 2011-03-30 18:37 UTC (permalink / raw)
  To: pgsql-admin

Hi,

when I used the postgres login 'replication' as the account for streaming
replication I get the following error message:
2011-03-28 18:06:47 CEST FATAL:  could not connect to the primary server:
FATAL:  no pg_hba.conf entry for replication connection from host
"172.16.56.122", user "replication", SSL off

The corresponding pg_hba.conf entry was correct and there was no other
matching entry before that line.
# TYPE  DATABASE        USER            CIDR-ADDRESS            METHOD
host    replication     replication              172.16.56.122/32        md5

By changing the account name - everything worked as smoth as I am used to
with postgres.

Best Regards,
Uwe

^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: problem with an account name 'replication' for streaming replication
  2011-03-30 18:37 problem with an account name 'replication' for streaming replication Uwe Bartels <uwe.bartels@gmail.com>
@ 2011-03-30 20:43 ` raghu ram <raghuchennuru@gmail.com>
  2011-03-31 04:37   ` Re: problem with an account name 'replication' for streaming replication Uwe Bartels <uwe.bartels@gmail.com>
  1 sibling, 1 reply; 5+ messages in thread

From: raghu ram @ 2011-03-30 20:43 UTC (permalink / raw)
  To: Uwe Bartels <uwe.bartels@gmail.com>; +Cc: pgsql-admin

On Thu, Mar 31, 2011 at 12:07 AM, Uwe Bartels <uwe.bartels@gmail.com> wrote:

> Hi,
>
> when I used the postgres login 'replication' as the account for streaming
> replication I get the following error message:
> 2011-03-28 18:06:47 CEST FATAL:  could not connect to the primary server:
> FATAL:  no pg_hba.conf entry for replication connection from host
> "172.16.56.122", user "replication", SSL off
>
> The corresponding pg_hba.conf entry was correct and there was no other
> matching entry before that line.
> # TYPE  DATABASE        USER            CIDR-ADDRESS            METHOD
> host    replication     replication              172.16.56.122/32
> md5
>
> By changing the account name - everything worked as smoth as I am used to
> with postgres.
>

The standby server must have superuser access privileges required. could you
please check it,if the "replication" user having superuser privileges or
not.

--Raghu Ram



> Best Regards,
> Uwe
>

^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: problem with an account name 'replication' for streaming replication
  2011-03-30 18:37 problem with an account name 'replication' for streaming replication Uwe Bartels <uwe.bartels@gmail.com>
  2011-03-30 20:43 ` Re: problem with an account name 'replication' for streaming replication raghu ram <raghuchennuru@gmail.com>
@ 2011-03-31 04:37   ` Uwe Bartels <uwe.bartels@gmail.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Uwe Bartels @ 2011-03-31 04:37 UTC (permalink / raw)
  To: raghu ram <raghuchennuru@gmail.com>; +Cc: pgsql-admin

On 30 March 2011 22:43, raghu ram <raghuchennuru@gmail.com> wrote:

>
>
> On Thu, Mar 31, 2011 at 12:07 AM, Uwe Bartels <uwe.bartels@gmail.com>wrote:
>
>> Hi,
>>
>> when I used the postgres login 'replication' as the account for streaming
>> replication I get the following error message:
>> 2011-03-28 18:06:47 CEST FATAL:  could not connect to the primary server:
>> FATAL:  no pg_hba.conf entry for replication connection from host
>> "172.16.56.122", user "replication", SSL off
>>
>> The corresponding pg_hba.conf entry was correct and there was no other
>> matching entry before that line.
>> # TYPE  DATABASE        USER            CIDR-ADDRESS            METHOD
>> host    replication     replication              172.16.56.122/32
>> md5
>>
>> By changing the account name - everything worked as smoth as I am used to
>> with postgres.
>>
>
> The standby server must have superuser access privileges required. could
> you please check it,if the "replication" user having superuser privileges or
> not.
>
yes, i gave the replication user the login+superuser rights.
unfortunately i already deleted the account so i cannot double check.

Uwe


>
> --Raghu Ram
>
>
>
>> Best Regards,
>> Uwe
>>
>
>

^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: problem with an account name 'replication' for streaming replication
  2011-03-30 18:37 problem with an account name 'replication' for streaming replication Uwe Bartels <uwe.bartels@gmail.com>
@ 2011-03-31 02:53 ` Fujii Masao <masao.fujii@gmail.com>
  2011-03-31 04:45   ` Re: problem with an account name 'replication' for streaming replication Uwe Bartels <uwe.bartels@gmail.com>
  1 sibling, 1 reply; 5+ messages in thread

From: Fujii Masao @ 2011-03-31 02:53 UTC (permalink / raw)
  To: Uwe Bartels <uwe.bartels@gmail.com>; +Cc: pgsql-admin

On Thu, Mar 31, 2011 at 3:37 AM, Uwe Bartels <uwe.bartels@gmail.com> wrote:
> when I used the postgres login 'replication' as the account for streaming
> replication I get the following error message:
> 2011-03-28 18:06:47 CEST FATAL:  could not connect to the primary server:
> FATAL:  no pg_hba.conf entry for replication connection from host
> "172.16.56.122", user "replication", SSL off
>
> The corresponding pg_hba.conf entry was correct and there was no other
> matching entry before that line.
> # TYPE  DATABASE        USER            CIDR-ADDRESS            METHOD
> host    replication     replication              172.16.56.122/32        md5
>
> By changing the account name - everything worked as smoth as I am used to
> with postgres.

This is a constraint of streaming replication, and listed as a TODO item.
http://wiki.postgresql.org/wiki/TODO#Configuration_files

    Have pg_hba.conf consider "replication" special only in the database field
        * http://archives.postgresql.org/pgsql-hackers/2010-10/msg00632.php

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: problem with an account name 'replication' for streaming replication
  2011-03-30 18:37 problem with an account name 'replication' for streaming replication Uwe Bartels <uwe.bartels@gmail.com>
  2011-03-31 02:53 ` Re: problem with an account name 'replication' for streaming replication Fujii Masao <masao.fujii@gmail.com>
@ 2011-03-31 04:45   ` Uwe Bartels <uwe.bartels@gmail.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Uwe Bartels @ 2011-03-31 04:45 UTC (permalink / raw)
  To: Fujii Masao <masao.fujii@gmail.com>; +Cc: pgsql-admin

On 31 March 2011 04:53, Fujii Masao <masao.fujii@gmail.com> wrote:

> On Thu, Mar 31, 2011 at 3:37 AM, Uwe Bartels <uwe.bartels@gmail.com>
> wrote:
> > when I used the postgres login 'replication' as the account for streaming
> > replication I get the following error message:
> > 2011-03-28 18:06:47 CEST FATAL:  could not connect to the primary server:
> > FATAL:  no pg_hba.conf entry for replication connection from host
> > "172.16.56.122", user "replication", SSL off
> >
> > The corresponding pg_hba.conf entry was correct and there was no other
> > matching entry before that line.
> > # TYPE  DATABASE        USER            CIDR-ADDRESS            METHOD
> > host    replication     replication              172.16.56.122/32
> md5
> >
> > By changing the account name - everything worked as smoth as I am used to
> > with postgres.
>
> This is a constraint of streaming replication, and listed as a TODO item.
> http://wiki.postgresql.org/wiki/TODO#Configuration_files
>
>    Have pg_hba.conf consider "replication" special only in the database
> field
>        * http://archives.postgresql.org/pgsql-hackers/2010-10/msg00632.php
>
Thanks.
And Brendan was right:
<<

I suspect this is going to trip a lot of people up.  We could just
document it and tell people that if they want to use 'replication' as
a username, they'd better quote it in pg_hba.conf.

>>

best regards,
Uwe


>
> Regards,
>
> --
> Fujii Masao
> NIPPON TELEGRAPH AND TELEPHONE CORPORATION
> NTT Open Source Software Center
>

^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2011-03-31 04:45 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2011-03-30 18:37 problem with an account name 'replication' for streaming replication Uwe Bartels <uwe.bartels@gmail.com>
2011-03-30 20:43 ` raghu ram <raghuchennuru@gmail.com>
2011-03-31 04:37   ` Uwe Bartels <uwe.bartels@gmail.com>
2011-03-31 02:53 ` Fujii Masao <masao.fujii@gmail.com>
2011-03-31 04:45   ` Uwe Bartels <uwe.bartels@gmail.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox