This post is more than 5 years old
1 Rookie
•
120 Posts
0
4056
November 28th, 2012 10:00
ERROR: Source and Destination servers are identical. Use --checkservers=false to force replication.
One of our implementation guys ran into an issue where replication was complaining that the replication target is an identical system. Seems like the system ID is the same on both nodes ? Is this a realistic possibility ? Can he change a system ID on the replication target or should he re-kickstart the node ?
System ID 1353958011@D4:AE:52:6A:23:85 is from 192.168.50.128
System ID 1353958011@D4:AE:52:6F:08:4A is from 192.168.15.128
No Events found!
ionthegeek
2 Intern
•
2K Posts
0
November 28th, 2012 11:00
Thanks Rob. It is only checking the create time so the shortest path to resolution will probably be a re-kick of one node or the other.
Honestly, I'm impressed that somebody managed to initialize two systems that are replicating to one another in the exact same second. The odds against that have to be pretty astronomical!
ionthegeek
2 Intern
•
2K Posts
1
November 28th, 2012 11:00
This is likely to be an issue with the probe.xml file. If the GSAN doesn't have an up to date list of node IPs, it may incorrectly return the internal IP of one or more of the nodes and the grid will end up talking to itself without realizing it.
Please don't follow the advice about checkservers as this is likely to cause serious problems on the source grid.
rob_steele
1 Rookie
•
120 Posts
0
November 28th, 2012 11:00
Both nodes are single nodes in two different sites. I wasnt planning on using the checkservers switch, just needed to know if I needed to rekickstart the remote node or if I was able to modify the system ID
rob_steele
1 Rookie
•
120 Posts
0
November 28th, 2012 11:00
2012/11/28-11:26:07 Replicate [v4.2.0 08/01/11] (avmgr 60100.402) localserver.com to remoteserver.com (Wed Nov 28 11:26:07 EST 2012)
2012/11/28-11:26:07
-----------------------------------------------------------------------------------
2012/11/28-11:26:07
2012/11/28-11:26:07 bindir:""
2012/11/28-11:26:07 Running as 'admin' (effective UID=500) on 'localserver.com' initially in /usr/local/avamar
2012/11/28-11:26:07
2012/11/28-11:26:07 Source server is '1353958011'
2012/11/28-11:26:08 Destination server is '1353958011'
2012/11/28-11:26:08 ERROR: Source and Destination servers are identical. Use --checkservers=false to force replication.
2012/11/28-11:26:08 dpncron.pm::docmdout got exit code 2304 from 'replicate --flagfile=/usr/local/avamar/etc/repl_cron.cfg', returning 0
2012/11/28-11:26:08 ======== failed replication (pid=21173) ========
2012/11/28-11:26:08 mccli event publish --code=4602 --message='repl_cron - failed replication (pid=21173)'
2012/11/28-11:26:15 0,23000,CLI command completed successfully.
2012/11/28-11:26:15
2012/11/28-11:26:15 avmaint infomessage --avamaronly --errcode=4602 'repl_cron - failed replication (pid=21173)'
2012/11/28-11:26:16 ============================== Finished repl_cron ==============================
2012/11/28-11:26:16
ionthegeek
2 Intern
•
2K Posts
1
November 28th, 2012 11:00
You can't change the systemid (it's immutable).
Could you please post 10 or 15 lines from the replicate.log leading up to the error? These two systems have the same create time (which is unusual) but I don't recall offhand if the replicator checks the full systemid or only the create time.
ionthegeek
2 Intern
•
2K Posts
0
November 28th, 2012 12:00
My pleasure!
rob_steele
1 Rookie
•
120 Posts
0
November 28th, 2012 12:00
I was thinking the same thing, I initially thought that they were trying to replicate to another port on the same node. Thanks Ian !
jtomas1
7 Posts
0
January 18th, 2013 07:00
Same issue, but multi node grids.
In my case I had bond3 for replication, but I had to use bond0, there goes ok.
Contact support for further details...