[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: Syncrepl and mmr

To: Quanah Gibson-Mount <quanah@zimbra.com>, "openldap-technical@openldap.org" <openldap-technical@openldap.org>
Subject: RE: Syncrepl and mmr
From: "Borresen, John - 0442 - MITLL" <John.Borresen@ll.mit.edu>
Date: Mon, 3 Feb 2014 13:06:59 -0500
Accept-language: en-US
Acceptlanguage: en-US
Content-language: en-US
In-reply-to: <301D280F978BB72758ED1FC4@[192.168.1.2]>
References: <1BB724A73E57084D89F6F28ED9E651920AD3170DFB@LLE2K7-BE02.mitll.ad.local> <201401301252.s0UCqYiG032646@boole.openldap.org> <BB8429D49E4807C586371E61@[192.168.1.2]> <20140130202839.1351AA624A@edge02.zimbra.com> <2B630E28DF38ECE010CBD25A@[192.168.1.2]> <20140130212629.B2597A6250@edge02.zimbra.com> <DB1FEF6327E2B46EC94F873B@[192.168.1.2]> <20140130213534.84D20A6263@edge02.zimbra.com> <395A5E98A0BA923103457A7D@[192.168.1.2]> <20140130215154.21246A6250@edge02.zimbra.com> <E05E339BB9E6991AE1EE9034@[192.168.1.2]> <20140131135522.883144425D@edge01.zimbra.com> <8B2D174F182D2F00973C48E7@[192.168.1.2]> <20140131182111.1FCCDA6244@edge02.zimbra.com> <DA81C395D0AF170D0D2E8E2A@[192.168.1.2]> <52EBF648.2030003@stroeder.com> <20140131192626.8EDCB44260@edge01.zimbra.com> <70B15C25BB69C8535EA2BF2E@[192.168.1.2]> <20140131193800.428F9A624B@edge02.zimbra.com> <4555DA4EB27A62A899B751DB@[192.168.1.2]> <20140131213521.0E815A626E@edge02.zimbra.com> <89C7F52021B10496CDC11C3B@[192.168.1.2]> <20140203145812.66A5144228@edge01.zimbra.com> <301D280F978BB72758ED1FC4@[192.168.1.2]>
Thread-index: Ac8hAQoWZHVB2sDERk2mFVHtVxoEkAABmAWw
Thread-topic: Syncrepl and mmr

The "cn=replicator,cn=accesslog" was the olcRootDN for the accesslog.

Rather that was my intent.

Rereading documentation...and the script you shared with me a few weeks back.

Currently, my set up is:
1) The rootDN for the cn=config is cn=admin (cn=admin,cn=config)
2) the rootDN for my primary dbase is cn=ldapadmin (cn=ldapadmin,dc=example,dc=ldap)
3) the rootDN for the accesslog, as mentioned above, is/was cn=replicator (cn=replicator,cn=accesslog)

My ou=Users,dc=example,dc=ldap has all the End-Users uids for logins.  

Noticed you have a cn=admins,cn=zimbra.

Bear with the stupid question, this is more of a sanity check for me (getting pressure from my side to get this project done -- so very rushed).

I could/should create an "ou=Admins,dc=example,dc=ldap", on both MM-Servers

In that ou create/move the replicator that I wrongfully created in cn=accesslog:

uid=replicator,ou=Admins,dc=example,dc=ldap

That will get this user in the dbase.

Modify, the olcSyncrepl, olcAccess, etc on both MM-Servers.

Is that basically, correct?

-----Original Message-----
From: Quanah Gibson-Mount [mailto:quanah@zimbra.com] 
Sent: Monday, February 03, 2014 11:57 AM
To: Borresen, John - 0442 - MITLL; openldap-technical@openldap.org
Subject: RE: Syncrepl and mmr

--On Monday, February 03, 2014 9:57 AM -0500 "Borresen, John - 0442 - MITLL" <John.Borresen@ll.mit.edu> wrote:

> All,
>
> I turned off TLS on both MMR machines, so I could more easily 
> troubleshoot Syncrepl/MMR configuration.  Once over this hurdle, I'll 
> re-incorporate TLS.
>
> The following is a snippet of the SLAPD output-log file:
>
> <MM-SERVER2>
> 52efa558 => bdb_dn2id("cn=replicator,cn=accesslog")
> 52efa558 <= bdb_dn2id: get failed: DB_NOTFOUND: No matching key/data 
> pair found (-30989) 52efa558 send_ldap_result: conn=5226 op=0 p=3
> 52efa558 send_ldap_result: err=49 matched="" text=""

What is cn=replicator,cn=accesslog?  Whatever it is, it doesn't exist in your DB.

--Quanah

--

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

References:
- RE: Syncrepl and mmr
  - From: Quanah Gibson-Mount <quanah@zimbra.com>

Prev by Date: Re: Deprecation of back-bdb
Next by Date: RE: Syncrepl and mmr
Index(es):
- Chronological
- Thread