From: John Scalia <jayknowsunix@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Cannot rebuild a standby server
Date: Fri, 20 Jun 2014 13:44:50 -0400
Message-ID: <53A47312.9040600@gmail.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
In the true definition of insanity, I've tried to rebuild a standby streaming replication server using the following steps several times:
1) ensure the postgresql data directory, /var/lib/pgsql/9.3/data, is empty.
2) run: pg_basebackup -h <primary server> -D /var/lib/pgsql/9.3/data
3) manually copy the WAL's from the primary server's pg_xlog directory to the directory specified in the standby's recovery.conf restore_command.
4) rm any artifacts from the standby's new data directory like the backup_label file.
5) copy the saved recovery.conf into the standby's data directory and check it is accurate.
6) Start the database using "service postgresql-9.3 start"
Every time, however, the following appears in the pg_log/postgresql-Fri.log:
<timestamp> LOG: entering standby mode
<timestamp> LOG: restored log file "00000003.history"
<timestamp> LOG: invalid secondary checkpoint record
<timestamp> PANIC: could not locate a valid checkpoint record
All this was originally caused by testing the failover mechanism in pgpool. That didn't succeed and I'm trying to get the servers back to their original states. I've done this kind
of thing before, but don't know what's wrong with this effort. What have I missed?
--
Jay
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: jayknowsunix@gmail.com
Subject: Re: Cannot rebuild a standby server
In-Reply-To: <53A47312.9040600@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox