Univention Bugzilla – Bug 43564
Nagios-Monitoring needs a DNS entry for the client if it is added by ad tools
Last modified: 2022-06-27 17:48:59 CEST
The customer reported that a computer created by AD-Tools which should be activated for nagios monitoring, also needs a DNS entry. In AD Member Mode Windows dns is used, so this entry is not necessary in UCS. → In UMC you have to activate nagios and add a DNS entry.
The Windows client should create its DNS record via DDNS update. I don't know how the Nagios monitoring works, probably it would be good if it would not require anything else to work.
Just to make it clear - one MUST create a DNS entry in the Univention-LDAP if one wants to enable Nagios in the UMC. In AD member mode bind9 from UCS is normally not used and therefore this requirement should be avoided. The requirement should be changed to a check if the host is resolvable or not.
> The Windows client should create its DNS record via DDNS update. Yes, but sometimes you want to monitor a printer, a USV, a switch or router and those boxes are usually not capable of DDNS. Anyway, if I understand correctly, the listener module "nagios-server.py" writes a "host" configuration file for each host that should be monitored. The host configuration file MUST contain the IP address of the host. The listener module retrieves this information from the "aRecord" entry of the UDM computer object. And I guess this is empty in an AD Member mode scenario, which probably results in a non-existant host configuration file. AFAICS the listener module would also log "'NAGIOS-SERVER: missing aRecord ${DN}' in this case.
This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.