Problem: Upgrade to 5.2 failure: error while running slapadd: mdb_id2entry_put: mdb_put failed: MDB_MAP_FULL

Problem

During an upgrade from UCS 5.0-10 to UCS 5.2, the process failed while configuring slapd during the step from UCS 5.1 to UCS 5.2.

The database restore step (executed via slapadd from the LDIF dump) aborted due to an MDB map size limitation. As a result:

  • The upgrade was interrupted.
  • The system remained on UCS 5.1.
  • The LDAP database ended up empty.

Excerpt from /var/log/univention/updater.log

  Loading from /var/backups/slapd-2.4.57+dfsg-3+deb11u1A~5.1.0.202501151832: 
  - directory cn=internal... done.
  - chowning database directory (openldap:openldap)... done
  - directory cn=translog... failed.

Loading the database from the LDIF dump failed with the following
error while running slapadd:
    mdb_id2entry_put: mdb_put failed: MDB_MAP_FULL: Environment mapsize limit reached(-30792) "reqSession=2161835,cn=translog"
    => mdb_tool_entry_put: id2entry_add failed: err=80
    => mdb_tool_entry_put: txn_aborted! Internal error (80)
    slapadd: could not add entry dn="reqSession=2161835,cn=translog" (line=27737403): txn_aborted! Internal error (80)

Solution

The issue can be resolved by increasing the MDB map size in advance of starting the upgrade.
Please refer to the following Univention Help article for detailed instructions:
:point_right: Problem: MDB_MAP_FULL

Note: This is a currently a bug and documented here: 58620 – Upgrade to UCS 5.2: "mdb_put failed: MDB_MAP_FULL" -> empty LDAP

This topic was automatically closed after 24 hours. New replies are no longer allowed.