Univention Bugzilla – Bug 45685
No Nagios checks for mdb limit / effective size
Last modified: 2018-03-09 12:15:19 CET
To monitor larger environments it is necessary to check for the remaining capacity of the mdb database. The customer had several support cases where especially the database maxsize (ldap/database/mdb/maxsize) and listener cache size (listener/cache/mdb/maxsize) were exceeded. So, it would be very helpful to get Nagios checks for this mdb limits. E.g. The customer MDB LDAP limit: 12884901888, effective size: 6442450944, full: 50%
univention-nagios * added new nagios plugin check_univention_slapd_mdb_maxsize (check_univention_slapd_mdb_maxsize_suidwrapper), checks the total and free pages of the mdb ldap database (lmdb-utils) and returns warning if 75% or critical if 90% of the total pages are in use * 26univention-nagios-common.inst add new nagios service UNIVENTION_SLAPD_MDB_MAXSIZE * 30univention-nagios-client.inst add host to UNIVENTION_SLAPD_MDB_MAXSIZE (only dc) * not increased join script version, instead added to yaml how to enable the plugin for updates univention-nagios.yaml merged to 4.3-0
Ok, check and instructions in Advisory work. Changes are merged to UCS 4.3 too.
<http://errata.software-univention.de/ucs/4.2/289.html>
*** Bug 35422 has been marked as a duplicate of this bug. ***