|
Jim Nasby [mailto:Jim.Nasby@xxxxxxxxxxxxxx] wrote: >On 11/2/16 2:49 PM, Joanna Xu wrote: >> The replication is verified and works. My questions are what’s the
>> reason causing “cp: cannot stat >> `/opt/postgres/9.1/archive/000000010000000000000003': No such file or
>> directory” on STANDBY and how to fix it? >What instructions/tools did you use to setup replication? The following steps were involved in setting up the replication:
·
Stop the STANDBY database.
·
Start the hot backup on the MASTER database.
·
Push data to the STANDBY database.
·
Stop the hot backup on the MASTER database.
·
Reload with the new configuration on MASTER.
·
Setup new configuration on the STANDBY database.
·
Start the STANDBY database. Also, we see the message “LOG: terminating walsender process due to replication timeout”
in the logs on MASTER. Is this expected in the condition when the system is less busy or else?
Thanks, Joanna -----Original Message----- On 11/2/16 2:49 PM, Joanna Xu wrote: > The replication is verified and works. My questions are what’s the
> reason causing “cp: cannot stat > `/opt/postgres/9.1/archive/000000010000000000000003': No such file or
> directory” on STANDBY and how to fix it? What instructions/tools did you use to setup replication? > Also, it seems the startup > process stucks on “recovering 000000010000000000000004”, how to
> resolve it? As far as I know that's normal while in streaming mode. -- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble!
http://BlueTreble.com 855-TREBLE2 (855-873-2532) mobile: 512-569-9461 |
