Today after upgrading our UCS Installation to 5.0-2 we started getting alerts from cron every 5 minutes.
One issue was manually solved through mkdir -p /var/lib/prometheus/node-exporter
.
However we still get stacktraces from check_univention_s4_connector:
raceback (most recent call last):
File "/usr/share/univention-monitoring-client/scripts//check_univention_s4_connector", line 75, in <module>
S4Connector.main()
File "/usr/lib/python3/dist-packages/univention/monitoring/__init__.py", line 74, in main
self.write_metrics()
File "/usr/share/univention-monitoring-client/scripts//check_univention_s4_connector", line 71, in write_metrics
self.debug('Found %d reject(s)! Please check output of univention-s4connector-list-rejected.' % (rejects,))
AttributeError: 'S4Connector' object has no attribute 'debug'
run-parts: /usr/share/univention-monitoring-client/scripts//check_univention_s4_connector exited with return code 1
Traceback (most recent call last):
File "/usr/share/univention-monitoring-client/scripts//check_univention_samba_drs_failures", line 86, in <module>
CheckSambaDrsRepl.main()
File "/usr/lib/python3/dist-packages/univention/monitoring/__init__.py", line 74, in main
self.write_metrics()
File "/usr/share/univention-monitoring-client/scripts//check_univention_samba_drs_failures", line 65, in write_metrics
(info_type, info) = drsuapi.DsReplicaGetInfo(self.drsuapi_handle, 1, req1)
TypeError: cannot unpack non-iterable drsuapi.DsReplicaGetInfo object
run-parts: /usr/share/univention-monitoring-client/scripts//check_univention_samba_drs_failures exited with return code 1
Since I’m not quite sure if this is an issue resulting from a particular (mis)configuration on our side, or a general issue - I’m opening this thread (although at least the error-message could be a bit more helpful in finding the misconfiguration).
Glad to provider further information
Thanks !