Well...that was a "doh!" on my part. <lol>
One last stupid question for the evening. "slapcat" created the ldif, when slapadd-ing to the the secondary, should I remove the extra lines (ex. entryUUID, creatorsName,createTimeStamp)?
Thanks, John
-----Original Message----- From: Quanah Gibson-Mount [mailto:quanah@zimbra.com] Sent: Monday, February 03, 2014 4:03 PM To: Borresen, John - 0442 - MITLL; openldap-technical@openldap.org Subject: RE: Syncrepl and mmr
--On Monday, February 03, 2014 3:57 PM -0500 "Borresen, John - 0442 - MITLL" John.Borresen@ll.mit.edu wrote:
Hmmmmmmmm,
Taking your advice to reload the secondary from the primary...by creating master set of ldifs off of the primary (mm-server1):
On the primary (mm-server1): # slapcat -F /usr/local/openldap/etc/openldap/slapd.d -l # backup/example_ldap.ldif -b dc=example,dc=ldap 52f000f2 ldif_read_file: checksum error on "/usr/local/openldap/etc/openldap/slapd.d/cn=config.ldif" 52f000f2 bdb_monitor_db_open: monitoring disabled; configure monitor database to enable
On the secondary (mm-server2): the same command worked...
There is no indication here the command failed. All it is reporting is that someone modified cn=config.ldif by hand rather than correctly using ldapmodify.
--Quanah
--
Quanah Gibson-Mount Architect - Server Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration