[WAL-Archive recovery stuck on one log file]

From: Michael Anderson <michael(dot)anderson(at)elegosoft(dot)com>
To: pgsql-novice(at)postgresql(dot)org
Subject: [WAL-Archive recovery stuck on one log file]
Date: 2017-08-23 08:14:26
Message-ID: 7a4b465d-1304-ed63-47a5-2bf2b6f747c6@elegosoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

Hello,

I'm running a 9.4 server with wal archiving and streaming replication to
a hot standby.
The standby server was down for several days and needed log files that
were no longer available, so I copied the archived wal files from backup
to the slave and added

restore_command = 'cp archivedir/%f "%p"'

to the recovery.conf file, and restarted the server. At first, recovery
proceeded as expected:

2017-08-22 15:50:35 CEST [874-6] LOG: restored log file
"0000000100000008000000C1" from archive
2017-08-22 15:51:20 CEST [874-7] LOG: restored log file
"0000000100000008000000C2" from archive
2017-08-22 15:51:26 CEST [874-8] LOG: restored log file
"0000000100000008000000C3" from archive
2017-08-22 15:51:27 CEST [874-9] LOG: restored log file
"0000000100000008000000C4" from archive
2017-08-22 15:51:30 CEST [874-10] LOG: restored log file
"0000000100000008000000C5" from archive
2017-08-22 15:51:33 CEST [874-11] LOG: restored log file
"0000000100000008000000C6" from archive
2017-08-22 15:51:35 CEST [874-12] LOG: restored log file
"0000000100000008000000C7" from archive
2017-08-22 15:51:38 CEST [874-13] LOG: restored log file
"0000000100000008000000C8" from archive
2017-08-22 15:51:41 CEST [874-14] LOG: restored log file
"0000000100000008000000C9" from archive
2017-08-22 15:51:43 CEST [874-15] LOG: restored log file
"0000000100000008000000CA" from archive
2017-08-22 15:51:46 CEST [874-16] LOG: restored log file
"0000000100000008000000CB" from archive

...up until a certain point, at which it got stuck on one log file. The
server is recovering the same file again and again ad infinitum:

2017-08-23 09:28:38 CEST [2965-12499] LOG: restored log file
"000000010000000B0000008E" from archive
2017-08-23 09:28:43 CEST [2965-12500] LOG: restored log file
"000000010000000B0000008E" from archive
2017-08-23 09:28:48 CEST [2965-12501] LOG: restored log file
"000000010000000B0000008E" from archive
2017-08-23 09:28:53 CEST [2965-12502] LOG: restored log file
"000000010000000B0000008E" from archive
2017-08-23 09:28:58 CEST [2965-12503] LOG: restored log file
"000000010000000B0000008E" from archive
2017-08-23 09:29:03 CEST [2965-12504] LOG: restored log file
"000000010000000B0000008E" from archive
2017-08-23 09:29:08 CEST [2965-12505] LOG: restored log file
"000000010000000B0000008E" from archive
2017-08-23 09:29:13 CEST [2965-12506] LOG: restored log file
"000000010000000B0000008E" from archive
2017-08-23 09:29:18 CEST [2965-12507] LOG: restored log file
"000000010000000B0000008E" from archive
2017-08-23 09:29:23 CEST [2965-12508] LOG: restored log file
"000000010000000B0000008E" from archive

it's been doing this for about 18 hours now.

Any ideas on what might be causing this or how to fix it?

Thanks,

Mike

--
Michael Anderson
IT Services & Support

elego Software Solutions GmbH
Gustav-Meyer-Allee 25
Building 12.3 (BIG) room 227
13355 Berlin, Germany

phone +49 30 23 45 86 96 michael.anderson at elegosoft.com
fax +49 30 23 45 86 95 http://www.elegosoft.com

Geschaeftsfuehrer: Olaf Wagner, Sitz Berlin
Amtsgericht Berlin-Charlottenburg, HRB 77719, USt-IdNr: DE163214194

Browse pgsql-novice by date

  From Date Subject
Next Message Yann Salaün 2017-08-24 12:52:16 Does pg store all `timestamp with time zone` in localtime? Why?
Previous Message Michael Anderson 2017-08-23 08:06:45 [WAL Recovery: stuck recovering same log file forever]