Univention Bugzilla – Bug 32277
Documentation for nagios/client/allowedhosts missing
Last modified: 2019-02-14 12:13:00 CET
[Ticket#2013081921005623] CHECK_NRPE errors If the Nagios server is installed on a different system then "ldap/master", the nagios server FQDN needs to be set via UCR(-Policy) "nagios/client/allowedhosts" on every Nagios client. This should be mentioned in the manual as customers will get misleading "CHECK_NRPE: Error - Could not complete SSL handshake" error messages for most of the checks as the nagios server is not allowed to connect.
This was part of the troubleshooting section within the old UCS 2.4 nagios manual: http://www.univention.de/fileadmin/download/dokumentation_2.4/ucs-nagios_101209.pdf
Again: 2014040821000851
I increase the priority as I'm discussing this about 3-4 times per year with someone...
I've added a paragraph to the Nagios manual. git.knut.univention.de:univention/ucs.git 373dfbc5f6..4eae39208c stefan/docu-cleanup -> stefan/docu-cleanup Jenkins Build: http://jenkins.knut.univention.de:8080/view/Doku/job/BuildDocBookBranch/43/artifact/webroot/manual-4.3.html#Nagios:Installation http://jenkins.knut.univention.de:8080/view/Doku/job/BuildDocBookBranch/43/artifact/webroot/handbuch-4.3.html#Nagios:Installation Please reopen the bug after the QA, so that I can merge it.
the text is OK, but i see "see ??? for more information" ??? should be a reference, is this normal?
(In reply to Felix Botner from comment #5) > the text is OK, but i see "see ??? for more information" ??? should be a > reference, is this normal? No, it is not normal. There was a typo in the xref. I've fixed and merged it.
(In reply to Stefan Gohmann from comment #6) > (In reply to Felix Botner from comment #5) > > the text is OK, but i see "see ??? for more information" ??? should be a > > reference, is this normal? > > No, it is not normal. There was a typo in the xref. I've fixed and merged it. → Verified
[master] dd16110 Bug #46874,Bug #32277,Bug #36733,Bug #39556,Bug #40162,Bug #41684,Bug #34726,Bug #41305,Bug #36869: PUBLISH