Univention Bugzilla – Bug 48543
univention-system-check does not check if s4-connector is running
Last modified: 2021-05-14 16:34:19 CEST
univention-system-check does not check if s4-connector is running. When started on a server (ie backup) it simply reports the misleading error from bug #48203 : running [basic] - FAILED - joinstatus.sh [...] Tests failed: 1 Test failed: univention-system-check.d/basic/joinstatus.sh, Impact: no domain functionallity + IMPACT='no domain functionallity' + univention-check-join-status Warning: 'univention-s4-connector' is not configured. Error: Not all install files configured: 1 missing root@solid:~# univention-s4connector-list-rejected Traceback (most recent call last): File "/usr/sbin/univention-s4connector-list-rejected", line 73, in <module> import mapping ImportError: No module named mapping Either univention-system-check should check if s4 connector is running and in this case ignore the error. Or bug #48203 should be fixed.
This issue has been filed against UCS 4.3. UCS 4.3 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.