Univention Bugzilla – Bug 37006
Monitoring of connectors
Last modified: 2015-12-28 16:15:48 CET
Currently, S4 connector and AD connector aren't monitored by Nagios. Since problems with these connectors, especially rejected objects, could cause unexpected and difficult to identify behaviour they should be monitored and reported to the Administrator.
bumped to 4.0
Requested during workshop.
For the AD connector we already have a plugin univention-nagios-ad-connector.
(In reply to Arvid Requate from comment #3)
> For the AD connector we already have a plugin univention-nagios-ad-connector.
Please provide a similar package for the S4 connector.
new package with nagios plugin to check the state of the s4 connector
* returns OK if connector/s4/autostart is not true
* returns CTRITICAL if univention-s4search fails
* returns CTRITICAL if connector is not running
* returns WARNING if rejects exists
added univention-nagios-s4-connector as Recommends
!!! announce univention-nagios-s4-connector before univention-s4-connector !!!
added univention-nagios-s4-connector to univention-dvd/tasks/ucs410/task-ucs410
added to univention-nagios-s4-connector triggers/ucs_4.1-0.txt
renamed YAML files to
It basically works but you don't use NRPE. Thus, the checks are always executed on the Master which doesn't make sense. See attached screenshot.
Created attachment 7351 [details]
fixed in univention-nagios-s4-connector 1.0.0-3.3.201512090901
OK, it works now.