Univention Bugzilla – Bug 47319
UNIVENTION_RAID returns "UNKNOWN: dm:[No devices to check];......"
Last modified: 2022-06-27 17:48:20 CEST
The handling of device mapper RAID is broken in check_raid as of UCS 4.3. The check always returns "UNKNOWN" state if no dm raid is configured (even if a mdraid is configured): UNKNOWN: dm:[No devices to check]; mdstat:[md3(2.73 TiB raid5):UUUU, md2(1023.44 MiB raid1):UUUU] So the check is currently nearly useless. See also: https://github.com/glensc/nagios-plugin-check_raid/pull/172 https://github.com/glensc/nagios-plugin-check_raid/issues/142 Temporary workaround (one line!): sed -i -re 's,/usr/lib/nagios/plugins/check_raid$,/usr/lib/nagios/plugins/check_raid -p mdstat,' /etc/nagios/nrpe.univention.d/UNIVENTION_RAID.cfg Then restart the NRPE daemon: "service nagios-nrpe-server restart" We should consider to ship univention-nagios-raid with "-p mdstat" als default arguments for check_raid.
The customer would like the fix within the next 2 weeks. Is that realistic?
univention-nagios-raid: e369348b2bcb33b7fe00b3880a8c51115fff30b7 yaml: 4bf5f2ec9d5aa5c179636954095be27ccba7ce28 We now always use "check_raid -p mdstat" (and no longer the dm plugin, if that is a problem, we have to make it configurable in the future). For updates, we simply fix the /etc/nagios/nrpe.univention.d/UNIVENTION_RAID.cfg (which is generated by a listener handler) and restart the nrpe server. New installations should use the modified command in "etc/nagios-plugins/config/univention-raid.cfg" directly. See nagios/univention-nagios-raid/test.txt for information about how to setup a raid.
OK: adapted check works for working, broken, rebuilding raid OK: Config is fixed during update OK: yaml Verified
<http://errata.software-univention.de/ucs/4.3/243.html>