Ah, what a good night sleep will do. Re-reading yours and Howard's emails
from yesterday made a lot more sense this morning. Thanks, Quanah. Was able
to get that loaded.
Now, the messages have changed, showing this one in the Consumer's messages
file:
--> do_syncrep2: rid=001 got empty syncUUID with LDAP_SYNC_ADD
The following is on the Provider...but, not 100% certain it pertains to the
synchronization, at all.
=> send_search_entry: conn 5806
dn="reqStart=20120307150423.000000Z,cn=accesslog"
<= send_search_entry: conn 5806 exit.
connection_close: conn=5806 sd=51
Thanks
David Borresen
ph: 781-981-2954
email: john.d.borresen@ll.mit.edu
-----Original Message-----
From: Quanah Gibson-Mount [mailto:quanah@zimbra.com]
Sent: Tuesday, March 13, 2012 6:40 PM
To: Borresen, John - 0442 - MITLL
Cc: openldap-technical@openldap.org
Subject: RE: OPENLDAP SYNCREPL
--On Tuesday, March 13, 2012 4:10 PM -0400 "Borresen, John - 0442 - MITLL"
<john.borresen@ll.mit.edu> wrote:
> My apologies for sounding stupid...but, I really don't see it. Out of
> utter frustration, I have tried to run it on nearly all the dn's that I
> can find all with the same "objectClass: value #1 invalid syntax error".
>
> I look at my overlay=syncprov and compare it to what you sent me they look
> identical. I'm not trying to sound stupid...
What you list as "MINE" is the one for the primary DB, *not* the accesslog
DB. As I said, you need to ADD an additional syncprov overlay setting TO
the accesslog DB. Since your accesslog DB is your SECOND BDB database, it
would be along the lines of:
dn: olcOverlay={0}syncprov,olcDatabase={2}bdb,cn=config
changetype:add
objectClass: olcOverlayConfig
objectClass: olcSyncProvConfig
olcOverlay: {0}syncprov
olcSpNoPresent: TRUE
olcSpReloadHint: TRUE
--Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
Attachment:
smime.p7s
Description: S/MIME cryptographic signature