Results 1 to 6 of 6

Thread: ldap master replacement.. replica is still looking for the old master.

  1. #1
    NathanL is offline Loyal Member
    Join Date
    Apr 2009
    Posts
    93
    Rep Power
    6

    Default [SOLVED] ldap master replacement.. replica is still looking for the old master.

    ZCS 7.2.2. multi-server, i'm testing our upgrade path from 6.0.10 on RHEL5 to 8.0.x on RHEL6. I have this intermediary step where i'm on zcs 7.2.2, and in a mixed rhel5/rhel6 environment.

    I'm at the point where i;ve got my 6.0.10 dev environment up to 7.2.2, and ive joined two new zldap servers to the mix. The old rhel5 ldap servers were named zldap0.zdev and zldap1.zdev. The new rhel6 zldap servers are named zldap2.zdev, and zldap3.zdev.

    I started by adding the two new machines as replicas. Then i promoted zldap2.zdev to master, and took zldap0.zdev (the old master) offline.

    I followed Promoting Replica to LDAP Master - Zimbra :: Wiki

    This went smoothly, and in the end i took down zldap1 as well.

    However, it seems like my new replica, is still looking for the OLD master, and not the new one, despite my telling it to use the new master.

    I see the following in my /var/log/zimbra.log

    Code:
    May 15 16:14:01 zldap3 slapd[21400]: slap_client_connect: URI=ldap://zldap0.zdev.lafayette.edu:389 Error, ldap_start_tls failed (-1)
    May 15 16:14:01 zldap3 slapd[21400]: do_syncrepl: rid=100 rc -1 retrying
    May 15 16:14:07 zldap3 slapd[21400]: connection_input: conn=1113 deferring operation: binding
    zmlocalconfig tells me that things look fine.

    Code:
    [zimbra@zldap3 DEV ~]$ zmlocalconfig ldap_url
    ldap_url = ldap://zldap3.zdev.lafayette.edu:389 ldap://zldap2.zdev.lafayette.edu:389
    [zimbra@zldap3 DEV ~]$ zmlocalconfig ldap_master_url
    ldap_master_url = ldap://zldap2.zdev.lafayette.edu:389
    What am i missing?
    Last edited by NathanL; 05-31-2013 at 08:54 AM.

  2. #2
    quanah is offline Zimbra Employee
    Join Date
    May 2007
    Location
    Zimbra
    Posts
    1,265
    Rep Power
    10

    Default

    This is because the URL to talk to is stored in the cn=config database of the replica, and is not trivial to change. It is possible to change it with libexec/zmldapreplicatool

    --Quanah
    Quanah Gibson-Mount
    Server Architect
    Zimbra, Inc
    --------------------
    Zimbra :: the leader in open source messaging and collaboration

  3. #3
    NathanL is offline Loyal Member
    Join Date
    Apr 2009
    Posts
    93
    Rep Power
    6

    Default

    Would it be easier to simply reinstall my replica?

    If that;s the case, would it have been smarter to install my new ldap master, promote it, and THEN build my new replica?

  4. #4
    NathanL is offline Loyal Member
    Join Date
    Apr 2009
    Posts
    93
    Rep Power
    6

    Default

    Also, shouldnt that be covered in the linked zimbra ldap server replica promotion wiki?

  5. #5
    quanah is offline Zimbra Employee
    Join Date
    May 2007
    Location
    Zimbra
    Posts
    1,265
    Rep Power
    10

    Default

    Quote Originally Posted by NathanL View Post
    Also, shouldnt that be covered in the linked zimbra ldap server replica promotion wiki?
    It is already on the wiki. See step "j".
    Quanah Gibson-Mount
    Server Architect
    Zimbra, Inc
    --------------------
    Zimbra :: the leader in open source messaging and collaboration

  6. #6
    NathanL is offline Loyal Member
    Join Date
    Apr 2009
    Posts
    93
    Rep Power
    6

    Default

    Quote Originally Posted by quanah View Post
    It is already on the wiki. See step "j".

    Quote Originally Posted by FromTheWiki
    j. Use the tool zmldapreplicatool to update the LDAP Master URI in the syncrepl configuration for each replica (ZCS 7.x only)
    I can understand why i missed it... that's a tad vague... Considering how well written and easy to follow the rest of the doc was, i'd sort of assumed it would have told me where zmldapreplicatool was, and how i might actually use it.

    For future reference (zldap3 is the replica, zldap2 is the master):

    Code:
    [zimbra@zldap3 DEV ~]$ libexec/zmldapreplicatool 
    [zimbra@zldap3 DEV ~]$ libexec/zmldapreplicatool --help
      zmldapreplicatool [-r RID] [-m masterURI] [-t critical|off]
    
      Where:
      -r: RID is a unique Integer Replication ID for this replication instance.  It must be unique inside this server.  Example: 100 Default: 100.  Generally no need to change this.
      -m: masterURI is the LDAP URI for the master.  Example: ldap://ldap-master.example.com:389/
      -t: set startTLS to critical (required) or off (disabled)
    
    [zimbra@zldap3 DEV ~]$ libexec/zmldapreplicatool -m ldap://zldap2.zdev.lafayette.edu:389/
    
    [zimbra@zldap3 DEV ~]$ zmcontrol restart
    Host zldap3.zdev.lafayette.edu
    	Stopping zmconfigd...Done.
    	Stopping stats...Done.
    
    ...
    
    	Stopping ldap...Done.
    Host zldap3.zdev.lafayette.edu
    	Starting ldap...Done.
    	Starting zmconfigd...Done.
    	Starting snmp...Done.
    	Starting stats...Done.
    [zimbra@zldap3 DEV ~]$
    I no longer see the error conencting to the old ldap master in my zimbra.log, and the updates which were not propagating to the replica, are now replicated.

    Thanks!

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Question regarding promoting ldap replica to master
    By chauvetp in forum Administrators
    Replies: 1
    Last Post: 11-23-2012, 08:47 PM
  2. Promoting Replica to LDAP Master for Zimbra 6 NE
    By americo in forum Installation
    Replies: 0
    Last Post: 07-18-2011, 01:57 PM
  3. [SOLVED] LDAP replica not connecting to master
    By CSVantage in forum Installation
    Replies: 0
    Last Post: 03-02-2011, 02:17 PM
  4. Replies: 11
    Last Post: 06-28-2010, 06:48 AM
  5. Multi-master LDAP replica
    By giedz in forum Administrators
    Replies: 1
    Last Post: 08-13-2009, 11:16 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •