Hi,
please keep the list posted, it might help other people too. I m
adding the list in cc.
from what you posted here below, my initial guess was right. You
need to make sure the file copy is unattended.
regards,
fabio pardi
On 16/01/2019 16:53, mallikarjun t
wrote:
Hi
Mallikarjunarao,
Wild guess: you missed to exchange the SSH key between
servers.
To find out where the problem is, you can try to run the
archive command
by hand and see the output. As in:
login on the master db as the user running postgres and try to
scp a
file to:
postgres@192.168.59.149:/home/postgres/data_archive
see what happens, and post it back here.
regards,
fabio pardi
On 1/16/19 4:38 PM, mallikarjun t wrote:
> Hi,
>
> This is Mallikarjunarao. Currently I am using PostgreSQL
9.6.10 version.
> In SSL streaming replication I am facing following
issues.
>
> alter system set archive_command to 'scp %p
> postgres@192.168.59.149:/home/postgres/data_archive/%f';
>
> <2019-01-15 21:38:38.648 IST [4599]>LOG:
connection received:
> host=192.168.59.149 port=41464
> <2019-01-15 21:38:38.656 IST [4599]>LOG:
replication connection
> authorized: user=postgres
> Permission denied, please try again.
> Permission denied, please try again.
> Permission denied
(publickey,gssapi-keyex,gssapi-with-mic,password).
> lost connection
> <2019-01-15 21:38:38.950 IST [4333]>LOG: archive
command failed with
> exit code 1
> <2019-01-15 21:38:38.950 IST [4333]>DETAIL: The
failed archive command
> was: scp pg_xlog/000000010000000000000001
>
postgres@192.168.59.149:/home/postgres/data_archive/000000010000000000000001
>
>
> I am searching error information but I didn't know that?
Could you
> please help me out situation ?
>
> ThanksAndRegards,
> Mallikarjunarao.
> **//___^
|
