+++ This bug was initially created as a clone of Bug #58668 +++ background: Modifying a group with around 36k users failed with an ldap error: _ldap_modify: Other (e.g., implementation specific) error (80) _ The nagios check said: SLAPD MDB OK: Database /var/lib/univention-ldap/ldap operational (in fact 35.7%) There we had the default UCR: ldap/database/mdb/maxsize: 4295000000 After increasing the ldap/database/mdb/maxsize: 5295000000 the group could be modified. The nagios check itself was misleading. We should adjust the warning levels for nagios and prometheus checks. > A good rule of thumb is to multiply the total database size by five. https://www.symas.com/post/openldap-lmdb-sizing-guide The administrator has no idea which group sizes/(other operations?) are "OK" for which ldap database size. Is there a way to estimate whether the remaining available space is enough to allow for modifications of present ldap objects? (At least for the largest object in LDAP). If so we should provide a monitoring script.
Backport of Bug #58668 to 5.0-10 8ed6dd08fc5 | feat(nagios): Improve check_univention_slapd_mdb_maxsize d8fbe5505d2 | feat(monitoring): Improve alerts/check_univention_mdb_maxsize Package: univention-nagios Version: 13.0.11-1 Release: 5.0-0 Scope: errata5.0-10 Package: univention-monitoring-client Version: 1.0.8-1 Release: 5.0-0 Scope: errata5.0-10
Verified: * Backport merge * Package update * Functional check * Advisory
<https://errata.software-univention.de/#/?erratum=5.0x1333> <https://errata.software-univention.de/#/?erratum=5.0x1334>