Bad recovery: no pg_xlog/RECOVERYXLOG

From: Marcin Koziej <marcin(at)cahoots(dot)pl>
To: pgsql-admin(at)postgresql(dot)org
Subject: Bad recovery: no pg_xlog/RECOVERYXLOG
Date: 2017-10-25 16:50:32
Message-ID: d90474b1-6913-f3ff-d224-73fd931cdd98@cahoots.pl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi!

I try to setup continuous archiving with PG 9.6 according to this
documentation:
https://www.postgresql.org/docs/9.6/static/continuous-archiving.html

I have Postgres wal_archive set to replica, I have archive on and
archive command is properly copying WAL segments to backup storage.

Having this running, I make a successful tar base backup using
pg_basebackup.

I then stop the DB, remove the data directory, unpack base backup to it,
create recovery.conf with a proper restore_command, run the server, and get:

LOG:  database system was interrupted; last known up at 2017-10-25
15:47:37 UTC
LOG:  starting archive recovery
Object 'pg_small3/pg_xlog/RECOVERYXLOG.lzo' not found
Cannot download pg_xlog/RECOVERYXLOG.lzo
LOG:  invalid checkpoint record
FATAL:  could not locate required checkpoint record
HINT:  If you are not restoring from a backup, try removing the file
"/var/lib/postgresql/data/backup_label".
LOG:  startup process (PID 20) exited with exit code 1
LOG:  aborting startup due to startup process failure
LOG:  database system is shut down

The message about "pg_xlog/RECOVERYXLOG.lzo" is written out by
restore_command. Indeed, the file is not in the backup storage, and
pg_xlog/RECOVERYXLOG was NEVER sent there by archive_command (which
compresses and adds .lzo extension)!

What could I be doing wrong?

--
Marcin Koziej

GPG key: http://go.cahoots.pl/gpg/ Ϟ Twitter: @movonw

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Marcin Koziej 2017-10-25 17:25:20 Re: Bad recovery: no pg_xlog/RECOVERYXLOG
Previous Message bend 2017-10-25 16:05:58 Re: Migrate from Oracle 12g to PostgreSQL 9.3