From: | Patrick Baker <patrickbakerbr(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | WAL segment NOT FOUND - Postgres 9.2 |
Date: | 2016-06-02 01:49:30 |
Message-ID: | CAJNY3ivsLkA4JjU+6+WuH1Kq-n6wfiCh_Jb4POrq50ZX2+iHUw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi guys,
I got one master and two slaves.
- slave01 = replication from master - working fine
- slave02 = server is configured to delay for 345600 seconds (4 days).
The issue is on the slave02 server
*Recovery.conf:*
restore_command = 'exec nice -n 19 ionice -c 2 -n 7 ../../bin/segment.sh
"../wal_archive/%f" "%p" 345600'
At about 10 days ago, I had an issue with my MASTER, and the server had to
be restarted.
*PROBLEM:*
The replication on the slave02 server is not working. When looking the
logs, I see:
WAL segment `../wal_archive/00000002000011E800000012` not found
I tried to copy manually that file, from my backups, then I get another
error:
Archived WAL segment `../wal_archive/00000002000011E800000012` is
newer than the configured delay (345600 seconds)
So it seems the database hasn't been replicated since MAY 17:
*on slave02 server:*
ls -la /var/lib/pgsql/9.2/wal_archive:
postgres postgres 16777216 May 17 18:16 00000002000011E80000000F
postgres postgres 16777216 May 17 18:18 00000002000011E800000010
postgres postgres 16777216 May 17 18:18 00000002000011E800000011
- Is there anything I can do to solve the problem? Without having to syn
all the DATABASE again?
From | Date | Subject | |
---|---|---|---|
Next Message | Ian Barwick | 2016-06-02 02:35:55 | Re: WAL segment NOT FOUND - Postgres 9.2 |
Previous Message | Michael JOIGNY | 2016-05-31 14:39:35 | could not read block 0 in file "base/mydb/myfile": read only 0 of 8192 bytes |