Just FYI, current master is utterly broken with back-mdb. Most sub-databases are missing.
mdb database with 2.4.35: zimbra@zre-ldap002:~/data/ldap/mdb/db$ mdb_stat -eaf . | grep "Status of" Status of Main DB Status of DKIMIdentity Status of DKIMSelector Status of ad2i Status of cn Status of displayName Status of dn2i Status of entryCSN Status of entryUUID Status of givenName Status of id2e Status of mail Status of objectClass Status of sn Status of uid Status of zimbraACE Status of zimbraAuthKerberos5Realm Status of zimbraCalResBuilding Status of zimbraCalResCapacity Status of zimbraCalResFloor Status of zimbraCalResRoom Status of zimbraCalResSite Status of zimbraDomainAliasTargetId Status of zimbraDomainName Status of zimbraForeignPrincipal Status of zimbraId Status of zimbraMailAlias Status of zimbraMailCatchAllAddress Status of zimbraMailDeliveryAddress Status of zimbraMailForwardingAddress Status of zimbraMailHost Status of zimbraMailTransport Status of zimbraMemberOf Status of zimbraShareInfo Status of zimbraSharedItem Status of zimbraUCServiceId Status of zimbraVirtualHostname Status of zimbraVirtualIPAddress Status of zimbraYahooId
mdb database with master: zimbra@zre-ldap001:~/data/ldap/mdb/db$ mdb_stat -eaf . | grep "Status of" Status of Main DB Status of DKIMIdentity Status of DKIMSelector Status of ad2i Status of cn
--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
Quanah Gibson-Mount wrote:
Just FYI, current master is utterly broken with back-mdb. Most sub-databases are missing.
Not seeing any problem here, or on ada.openldap.org. You must have a corrupted build tree.
mdb database with 2.4.35: zimbra@zre-ldap002:~/data/ldap/mdb/db$ mdb_stat -eaf . | grep "Status of" Status of Main DB Status of DKIMIdentity Status of DKIMSelector Status of ad2i Status of cn Status of displayName Status of dn2i Status of entryCSN Status of entryUUID Status of givenName Status of id2e Status of mail Status of objectClass Status of sn Status of uid Status of zimbraACE Status of zimbraAuthKerberos5Realm Status of zimbraCalResBuilding Status of zimbraCalResCapacity Status of zimbraCalResFloor Status of zimbraCalResRoom Status of zimbraCalResSite Status of zimbraDomainAliasTargetId Status of zimbraDomainName Status of zimbraForeignPrincipal Status of zimbraId Status of zimbraMailAlias Status of zimbraMailCatchAllAddress Status of zimbraMailDeliveryAddress Status of zimbraMailForwardingAddress Status of zimbraMailHost Status of zimbraMailTransport Status of zimbraMemberOf Status of zimbraShareInfo Status of zimbraSharedItem Status of zimbraUCServiceId Status of zimbraVirtualHostname Status of zimbraVirtualIPAddress Status of zimbraYahooId
mdb database with master: zimbra@zre-ldap001:~/data/ldap/mdb/db$ mdb_stat -eaf . | grep "Status of" Status of Main DB Status of DKIMIdentity Status of DKIMSelector Status of ad2i Status of cn
--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
--On Saturday, April 06, 2013 5:09 AM -0700 Howard Chu hyc@symas.com wrote:
Quanah Gibson-Mount wrote:
Just FYI, current master is utterly broken with back-mdb. Most sub-databases are missing.
Not seeing any problem here, or on ada.openldap.org. You must have a corrupted build tree.
Nope. My source is 100% identical to current master. It appears to be a bug in mdb_stat in current master:
OpenLDAP 2.4.35: zimbra@zre-ldap001:~$ ./libexec/zmslapadd /tmp/ldap-load-domains.ldif zimbra@zre-ldap001:~$ cd data/ldap/mdb/db zimbra@zre-ldap001:~/data/ldap/mdb/db$ mdb_stat -af . | grep "Status of" | wc -l 39
Current master: zimbra@zre-ldap001:~$ ./libexec/zmslapadd /tmp/ldap-load-domains.ldif _#################### 100.00% eta none elapsed none fast! Closing DB... zimbra@zre-ldap001:~$ cd data/ldap/mdb/db zimbra@zre-ldap001:~/data/ldap/mdb/db$ mdb_stat -af . | grep "Status of" | wc -l 5
However, if I use "mdb_stat" from OpenLDAP 2.4.35 WITH the DB created with openldap.master, I can see all indices:
zimbra@zre-ldap001:~/data/ldap/mdb/db$ /opt/zimbra/openldap-2.4.35.2z/bin/mdb_stat -af . | grep "Status of" | wc -l 39
vs zimbra@zre-ldap001:~/data/ldap/mdb/db$ /opt/zimbra/openldap/bin/mdb_stat -af . | grep "Status of" | wc -l 5
--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
Quanah Gibson-Mount wrote:
--On Saturday, April 06, 2013 5:09 AM -0700 Howard Chu hyc@symas.com wrote:
Quanah Gibson-Mount wrote:
Just FYI, current master is utterly broken with back-mdb. Most sub-databases are missing.
Not seeing any problem here, or on ada.openldap.org. You must have a corrupted build tree.
Nope. My source is 100% identical to current master. It appears to be a bug in mdb_stat in current master:
OK, that narrowed it down. Fixed now in master/mdb.master.
OpenLDAP 2.4.35: zimbra@zre-ldap001:~$ ./libexec/zmslapadd /tmp/ldap-load-domains.ldif zimbra@zre-ldap001:~$ cd data/ldap/mdb/db zimbra@zre-ldap001:~/data/ldap/mdb/db$ mdb_stat -af . | grep "Status of" | wc -l 39
Current master: zimbra@zre-ldap001:~$ ./libexec/zmslapadd /tmp/ldap-load-domains.ldif _#################### 100.00% eta none elapsed none fast! Closing DB... zimbra@zre-ldap001:~$ cd data/ldap/mdb/db zimbra@zre-ldap001:~/data/ldap/mdb/db$ mdb_stat -af . | grep "Status of" | wc -l 5
However, if I use "mdb_stat" from OpenLDAP 2.4.35 WITH the DB created with openldap.master, I can see all indices:
zimbra@zre-ldap001:~/data/ldap/mdb/db$ /opt/zimbra/openldap-2.4.35.2z/bin/mdb_stat -af . | grep "Status of" | wc -l 39
vs zimbra@zre-ldap001:~/data/ldap/mdb/db$ /opt/zimbra/openldap/bin/mdb_stat -af . | grep "Status of" | wc -l 5
--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