HI!
What are the possible reasons for this message?
5070a03c backend_startup_one (type=mdb, suffix="cn=accesslog,o=example"): bi_db_open failed! (-30793)
I'm testing migrating an existing LDAP server with four DBs - two of them accesslog DBs - to back-mdb with RE24 c62a82b07e1bcc4c795cb5185ee9f16406b05bd9.
Either slapadd fails or starting slapd fails after slapadd.
Ciao, Michael.
--On Saturday, October 06, 2012 11:22 PM +0200 Michael Ströder michael@stroeder.com wrote:
HI!
What are the possible reasons for this message?
5070a03c backend_startup_one (type=mdb, suffix="cn=accesslog,o=example"): bi_db_open failed! (-30793)
I'm testing migrating an existing LDAP server with four DBs - two of them accesslog DBs - to back-mdb with RE24 c62a82b07e1bcc4c795cb5185ee9f16406b05bd9.
Either slapadd fails or starting slapd fails after slapadd.
Can you supply your configuration (minus passwords)? Generally this would only happen if two databases had the same directory listed for their DB.
--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, October 06, 2012 11:22 PM +0200 Michael Ströder michael@stroeder.com wrote:
What are the possible reasons for this message?
5070a03c backend_startup_one (type=mdb, suffix="cn=accesslog,o=example"): bi_db_open failed! (-30793)
I'm testing migrating an existing LDAP server with four DBs - two of them accesslog DBs - to back-mdb with RE24 c62a82b07e1bcc4c795cb5185ee9f16406b05bd9.
Either slapadd fails or starting slapd fails after slapadd.
Can you supply your configuration (minus passwords)? Generally this would only happen if two databases had the same directory listed for their DB.
I'm currently very busy => currently no spare time to draw an example config.
This particular accesslog data contains few entries which have obsolete schema elements in attribute 'reqMod'. Schema checking forbids to load these entries so I use "slapadd -c" to ignore this entries. This works well with back-hdb. Now I suspect that back-mdb does not handle this case correctly. But I have to dig into this a bit more.
Ciao, Michael.
Michael Ströder wrote:
Quanah Gibson-Mount wrote:
--On Saturday, October 06, 2012 11:22 PM +0200 Michael Ströder michael@stroeder.com wrote:
What are the possible reasons for this message?
5070a03c backend_startup_one (type=mdb, suffix="cn=accesslog,o=example"): bi_db_open failed! (-30793)
I'm testing migrating an existing LDAP server with four DBs - two of them accesslog DBs - to back-mdb with RE24 c62a82b07e1bcc4c795cb5185ee9f16406b05bd9.
Either slapadd fails or starting slapd fails after slapadd.
Can you supply your configuration (minus passwords)? Generally this would only happen if two databases had the same directory listed for their DB.
I'm currently very busy => currently no spare time to draw an example config.
Ah, of course. None of *us* are very busy. We have all the time in the world to chase down your inadequately documented questions.
This particular accesslog data contains few entries which have obsolete schema elements in attribute 'reqMod'. Schema checking forbids to load these entries so I use "slapadd -c" to ignore this entries. This works well with back-hdb. Now I suspect that back-mdb does not handle this case correctly. But I have to dig into this a bit more.
The error code -30793 MDB_INVALID comes from libmdb and means exactly that: the files you pointed at are not valid MDB files. This is a low level error and no schema error in back-mdb would produce it.
openldap-technical@openldap.org
-
Howard Chu -
Michael Ströder -
Quanah Gibson-Mount