[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Reasons for bi_db_open failed! (-30793) with back-mdb?

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

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.

  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/