Postgresql 9.3 hotstandby replication error, icorrect checksome in control file
Hi everyone,
I am trying to setup postgresql 9.3 hotstandby replication server. I am
getting error incorrect checksome in control file. both server have below
version and pg package version and both are 64 bit processor.
OS is : Debian squeeze
PG version:- postgresql-9.3
Only difference is replication server hardware is more powerful than master
server.
I am following this link
http://www.rassoc.com/gregr/weblog/2013/02/16/zero-to-postgresql-streaming-replication-in-10-mins/.
I had done replication previously by using this method but in that cases
server hardware was same and OS was debian squeeze or it was on debian
wheezy on different hardwares or VPS servers.
Is there any different way to do replication to avoid this issue? or how
can I resolve this issue.
--
Regards
Amit Bondwal
Detailed logs in log file
DETAIL: The primary's identifier is 6185381639353264094, the standby's
identifier is 6185382953613258663.
2015-08-21 15:34:16 IST [21447-1] FATAL: database system identifier
differs between the primary and standby
2015-08-21 15:34:16 IST [21447-2] DETAIL: The primary's identifier is
6185381639353264094, the standby's identifier is 6185382953613258663.
2015-08-21 15:34:17 IST [21105-2] LOG: received fast shutdown request
2015-08-21 15:34:17 IST [21105-3] LOG: aborting any active transactions
2015-08-21 15:34:17 IST [21107-1] LOG: shutting down
2015-08-21 15:34:17 IST [21107-2] LOG: database system is shut down
2015-08-21 15:34:18 IST [21465-1] LOG: database system was shut down in
recovery at 2015-08-21 15:34:17 IST
2015-08-21 15:34:18 IST [21465-2] LOG: entering standby mode
2015-08-21 15:34:18 IST [21465-3] LOG: consistent recovery state reached
at 0/1782DE8
2015-08-21 15:34:18 IST [21465-4] LOG: record with zero length at 0/1782DE8
2015-08-21 15:34:18 IST [21464-1] LOG: database system is ready to accept
read only connections
2015-08-21 15:34:18 IST [21469-1] FATAL: database system identifier
differs between the primary and standby
2015-08-21 15:34:18 IST [21469-2] DETAIL: The primary's identifier is
6185381639353264094, the standby's identifier is 6185382953613258663.
2015-08-21 15:34:19 IST [21470-1] [unknown]@[unknown] LOG: incomplete
startup packet
2015-08-21 15:34:33 IST [21492-1] FATAL: database system identifier
differs between the primary and standby
2015-08-21 15:34:33 IST [21492-2] DETAIL: The primary's identifier is
6185381639353264094, the standby's identifier is 6185382953613258663.
2015-08-21 15:34:38 IST [21495-1] FATAL: database system identifier
differs between the primary and standby
2015-08-21 15:34:38 IST [21495-2] DETAIL: The primary's identifier is
6185381639353264094, the standby's identifier is 6185382953613258663.
2015-08-21 15:34:43 IST [21496-1] FATAL:
2015-08-21 15:34:43 IST [21496-2] DETAIL: The primary's identifier is
6185381639353264094, the standby's identifier is 6185382953613258663.
2015-08-21 15:34:48 IST [21498-1] FATAL: "/var/lib/postgresql/9.3/main" is
not a valid data directory
2015-08-21 15:34:48 IST [21498-2] DETAIL: File
"/var/lib/postgresql/9.3/main/PG_VERSION" is missing.
2015-08-21 15:35:03 IST [21507-1] FATAL: database system identifier
differs between the primary and standby
2015-08-21 15:35:03 IST [21507-2] DETAIL: The primary's identifier is
6185381639353264094, the standby's identifier is 6185382953613258663.
2015-08-21 15:35:03 IST [21464-2] LOG: received fast shutdown request
2015-08-21 15:35:03 IST [21464-3] LOG: aborting any active transactions
2015-08-21 15:35:03 IST [21466-1] LOG: shutting down
2015-08-21 15:35:03 IST [21466-2] LOG: database system is shut down
2015-08-21 15:35:29 IST [21535-1] FATAL: incorrect checksum in control file
2015-08-21 15:40:20 IST [21561-1] FATAL: incorrect checksum in control file
It gives the error "database system identifier differs between the primary
and standby".
On Fri, Aug 21, 2015 at 3:26 PM, Amit Bondwal <bondwal.amit@gmail.com>
wrote:
Show quoted text
Hi everyone,
I am trying to setup postgresql 9.3 hotstandby replication server. I am
getting error incorrect checksome in control file. both server have below
version and pg package version and both are 64 bit processor.OS is : Debian squeeze
PG version:- postgresql-9.3Only difference is replication server hardware is more powerful than
master server.I am following this link
http://www.rassoc.com/gregr/weblog/2013/02/16/zero-to-postgresql-streaming-replication-in-10-mins/.
I had done replication previously by using this method but in that cases
server hardware was same and OS was debian squeeze or it was on debian
wheezy on different hardwares or VPS servers.Is there any different way to do replication to avoid this issue? or how
can I resolve this issue.--
RegardsAmit Bondwal
On Fri, Aug 21, 2015 at 7:56 PM, Amit Bondwal <bondwal.amit@gmail.com>
wrote:
2015-08-21 15:35:03 IST [21507-2] DETAIL: The primary's identifier is
6185381639353264094, the standby's identifier is 6185382953613258663.It gives the error "database system identifier differs between the primary
and standby".
This means that you are trying to use a standby that has been set up using
the base backup from the node of another cluster (be it either standby or
master node), different than the node you are trying to connect to. This
error just reports the incompatibility.
--
Michael
Michael, Thanks for your reply, I found the issue, the person who setup OS
mix up some 64 and 32 bit package. I am starting it again.
Thanks again.
On Fri, Aug 21, 2015 at 5:12 PM, Michael Paquier <michael.paquier@gmail.com>
wrote:
Show quoted text
On Fri, Aug 21, 2015 at 7:56 PM, Amit Bondwal <bondwal.amit@gmail.com>
wrote:2015-08-21 15:35:03 IST [21507-2] DETAIL: The primary's identifier is
6185381639353264094, the standby's identifier is 6185382953613258663.It gives the error "database system identifier differs between the
primary and standby".This means that you are trying to use a standby that has been set up using
the base backup from the node of another cluster (be it either standby or
master node), different than the node you are trying to connect to. This
error just reports the incompatibility.
--
Michael