Thanks Quanah for the prompt reply as you've always provided on this list.
Yes, just after I sent this, I realized the next question was going to be what version of OpenLDAP, which is, "OpenLDAP: slapd 2.4.39 "
Yes, I'm using hdb:
database hdb suffix "dc=example,dc=com" checkpoint 1024 15 rootdn "cn=Manager,dc=example,dc=com"
So, with 2.4.39 I should use ??? bdb or mdb? or?
And as mentioned about slapo-rwm, I'm using ldap proxy to Active Directory mapping to:
overlay rwm rwm-map objectclass posixAccount user rwm-map attribute uid sAMAccountName rwm-map attribute cn cn rwm-map attribute sn sn rwm-map attribute uidNumber uidNumber rwm-map attribute gidNumber gidNumber rwm-map attribute homeDirectory unixHomeDirectory rwm-map attribute loginShell loginShell rwm-map attribute mail mail rwm-map attribute * Is there a better way instead?
Thanks a bunch!
Sterling
------ Original Message ------ From: "Quanah Gibson-Mount" quanah@zimbra.com To: "Sterling Sahaydak" sterling.sahaydak@pi-coral.com; openldap-technical@openldap.org Sent: 7/9/2015 5:18:44 PM Subject: Re: Replication mode - glibc detected *** slapd: double free or corruption
--On Thursday, July 09, 2015 9:53 PM +0000 Sterling Sahaydak sterling.sahaydak@pi-coral.com wrote:
I've had replication working for the last few months and now running into the following when I run: slapd -h "ldapi:/// ldap:/// ldaps:///" -d 4
I installed GIT on the server, version 1.7.1 which is a couple years old, but was wondering would that have anything causing replication to stop working?
The openldap version is what is important, not the version of git. However, it looks like you have a corrupt database:
559edda4 hdb_db_open: database "dc=pi-coral,dc=com": unclean shutdown detected; attempting recovery.
back-hdb is deprecated in current OpenLDAP, and back-mdb is the supported backend. I also note you appear to be using slapo-rwm, which is known to have a variety of issues.
--Quanah
--
Quanah Gibson-Mount Platform Architect Zimbra, Inc.
Zimbra :: the leader in open source messaging and collaboration