You are right Dan, the ip has no bearing on it. I am just re-using the IP because it is tied in DNS to the name of my Master. Since the hubs refer to the master by DNS, I brought up the new machine with the same ip hoping that the hubs would not notice that the Master has moved to a new machine. However I am getting the following error.
[08/Jan/2013:19:15:40 -0800] NSMMReplicationPlugin - agmt="cn=add->hub" (rep12:2390): Replica was successfully acquired. [08/Jan/2013:19:15:40 -0800] NSMMReplicationPlugin - agmt="cn=add->hub" (rep12:2390): State: backoff -> sending_updates [08/Jan/2013:19:15:40 -0800] NSMMReplicationPlugin - agmt="cn=add->hub" (rep12:2390): Replica has a different generation ID than the local data. [08/Jan/2013:19:15:40 -0800] NSMMReplicationPlugin - agmt="cn=add->hub" (rep12:2390): Successfully released consumer [08/Jan/2013:19:15:40 -0800] NSMMReplicationPlugin - agmt="cn=add->hub" (rep12:2390): Beginning linger on the connection [08/Jan/2013:19:15:40 -0800] NSMMReplicationPlugin - agmt="cn=add->hub" (rep12:2390): State: sending_updates -> start_backoff [08/Jan/2013:19:15:44 -0800] NSMMReplicationPlugin - agmt="cn=add->hub" (rep12:2390): State: start_backoff -> backoff [08/Jan/2013:19:15:44 -0800] NSMMReplicationPlugin - agmt="cn=add->hub" (rep12:2390): Cancelling linger on the connection [08/Jan/2013:19:15:44 -0800] - _csngen_adjust_local_time: gen state before 50ece0dc0001:1357701340:0:0 [08/Jan/2013:19:15:44 -0800] - _csngen_adjust_local_time: gen state after 50ece0e00000:1357701344:0:0 [08/Jan/2013:19:15:44 -0800] NSMMReplicationPlugin - agmt="cn=add->hub" (rep12:2390): Replica was successfully acquired. [08/Jan/2013:19:15:44 -0800] NSMMReplicationPlugin - agmt="cn=add->hub" (rep12:2390): State: backoff -> sending_updates [08/Jan/2013:19:15:44 -0800] NSMMReplicationPlugin - agmt="cn=add->hub" (rep12:2390): Replica has a different generation ID than the local data. [08/Jan/2013:19:15:44 -0800] NSMMReplicationPlugin - agmt="cn=add->hub" (rep12:2390): Successfully released consumer I know the fix for this is re-initializing the hubs and reps, but if I want to circumvent that, I was hoping I could manually match the 'generation Ids' on the Master to the hubs. Unfortunately that does not seem to matter, since the function 'csngen_adjust_local_time' seems to be factoring in some other variables apart from the 'ReplicaGeneration' attribute in dse.ldif. ~thanks, Shar. From: 389-users-boun...@lists.fedoraproject.org [mailto:389-users-boun...@lists.fedoraproject.org] On Behalf Of Dan Lavu Sent: Monday, December 17, 2012 8:58 AM To: General discussion list for the 389 Directory server project. Subject: Re: [389-users] Swap Master Hardware. Did you use the IP when creating the replication agreement? The IP *should* have no bearing on it, at least thats what I thought. I'd be interested it know now, because I'll be moving a master soon. On Dec 16, 2012, at 8:50 PM, Shardul Kerkar <sker...@accessline.com<mailto:sker...@accessline.com>> wrote: Adding another Master is not an option because for the end result the IP address and dns record of the master should be same. I did try to swap the hardware on the existing Master after stopping writes and making sure that the db was in sync. After recreating replication agreements with the hubs, it is now complaining that the hubs have a different generation id, hence won't replicate. On Dec 16, 2012, at 6:52 AM, "Dan Lavu" <d...@lavu.net<mailto:d...@lavu.net>> wrote: You do not have to init the database as long as they are in sync, you can just 'send updates'. If all the slaves are 1.1.2, you'd want to eventually upgrade those machines too, have you considered just adding another master (master/master) then sliding the original master out? Should equate to zero downtime. On Dec 14, 2012, at 6:53 PM, Shardul Kerkar <sker...@accessline.com<mailto:sker...@accessline.com>> wrote: Hi Folks, I have recently been tasked with moving a Single Ldap Master from a dying machine to a spanking new blade. After doing some research it appears to me that the optimum way to do this will be installing a fresh instance of the application on the new server, import the database and then recreate and reinitialize all the hubs and replicas. The problem I face is that this work place has a humongous LDAP database will 3 mil+ entries. Re-initialization is taking upto 3 hours in some cases. With 5 hubs and 20 replicas to reinitialize, the downtime is unacceptable to the client. If I stop writes to the Master, then export the database to the new box and recreate the New-Master-Hub replication after removing the old Master , will I still need to re-initialize the hubs? Is there any way to do this swap without reinitializing or fooling the hubs and reps into thinking that they are still talking to the same Master albeit on a new machine (same ip address/dns). The client is still using ver. 1.1.2 on Centos 5.4 Thanks, Shar Ker -- 389 users mailing list 389-users@lists.fedoraproject.org<mailto:us...@lists.fedoraproject.org> https://admin.fedoraproject.org/mailman/listinfo/389-users <ATT00001..c> -- 389 users mailing list 389-users@lists.fedoraproject.org<mailto:us...@lists.fedoraproject.org> https://admin.fedoraproject.org/mailman/listinfo/389-users
-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
