Re: replication error

From: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "'Anton Gorlov *EXTERN*'" <stalker(at)altlinux(dot)ru>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: replication error
Date: 2017-02-28 15:23:51
Message-ID: A737B7A37273E048B164557ADEF4A58B53A00A20@ntex2010i.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Anton Gorlov wrote:
> I try setup replica from instructions located at
> https://wiki.postgresql.org/wiki/Streaming_Replication
>
>
> I copied data to slave, after psql -c "SELECT pg_start_backup('label', true)" and start slave - i
> see in logs many message like
>
> cp: cannot stat '/var/lib/postgresql/9.6/main/archive/000000010000000000000012': No such file or
> directory
> 2017-02-28 17:48:45 MSK [2333-3] LOG: redo starts at 0/12000098
> 2017-02-28 17:48:45 MSK [2333-4] LOG: consistent recovery state reached at 0/120000D0
> 2017-02-28 17:48:45 MSK [2333-5] LOG: record with incorrect prev-link 10000/2470000 at 0/120000D0
> 2017-02-28 17:48:45 MSK [2332-1] LOG: database system is ready to accept read only connections
> 2017-02-28 17:48:45 MSK [2339-1] LOG: started streaming WAL from primary at 0/12000000 on timeline 1
>
>
> on master node file 000000010000000000000012 located in pg_xlog directory and copy to archive
> diectory after execute
> psql -c "SELECT pg_stop_backup()" and after copy database data to slave.

Looks like everything is fine.

The standby recovered all WAL it could find in /var/lib/postgresql/9.6/main/archive/
and then connected to the primary for streaming replication.

000000010000000000000012 is not archived yet, so the standby cannot find it.

Test replication by changing something on the primary and checking if the
change gets replicated.

Yours,
Laurenz Albe

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message John Scalia 2017-03-01 15:32:38 Dealing with a cursor in libpq c program
Previous Message Anton Gorlov 2017-02-28 14:54:48 replication error