Univention Bugzilla – Bug 53900
systemdiagnose check shows a traceback in 44_well_known_sid_check
Last modified: 2022-01-28 17:18:09 CET
##################### Start 44_well_known_sid_check ##################### ## Check failed: 44_well_known_sid_check - Überprüfe 'Well Known' SIDs ## Traceback (most recent call last): File "/usr/lib/python3/dist-packages/univention/management/console/modules/diagnostic/plugins/44_well_known_sid_check.py", line 152, in check_existence_and_consistency actual_name = ldap_connection.get_by_sid(sid) File "/usr/lib/python3/dist-packages/univention/management/console/modules/diagnostic/plugins/44_well_known_sid_check.py", line 111, in get_by_sid raise KeyError(sid) KeyError: 'S-1-5-32-554' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/univention/management/console/modules/diagnostic/__init__.py", line 280, in execute result = execute(umc_module, **kwargs) File "/usr/lib/python3/dist-packages/univention/management/console/modules/diagnostic/plugins/44_well_known_sid_check.py", line 175, in run check_errors = list(check_existence_and_consistency()) File "/usr/lib/python3/dist-packages/univention/management/console/modules/diagnostic/plugins/44_well_known_sid_check.py", line 156, in check_existence_and_consistency yield SIDNotFound(error.message, mapped_name) AttributeError: 'KeyError' object has no attribute 'message' ###################### End 44_well_known_sid_check ###################### But the objectSID is okay, I think :~# univention-s4search objectSID=S-1-5-32-554 lpcfg_do_service_parameter: WARNING: The "blocking locks" option is deprecated lpcfg_do_service_parameter: WARNING: The "blocking locks" option is deprecated lpcfg_do_service_parameter: WARNING: The "blocking locks" option is deprecated lpcfg_do_service_parameter: WARNING: The "blocking locks" option is deprecated lpcfg_do_service_parameter: WARNING: The "blocking locks" option is deprecated lpcfg_do_service_parameter: WARNING: The "blocking locks" option is deprecated lpcfg_do_service_parameter: WARNING: The "blocking locks" option is deprecated lpcfg_do_service_parameter: WARNING: The "blocking locks" option is deprecated # record 1 dn: CN=Pre-Windows 2000 Compatible Access,CN=Builtin,DC=schein,DC=local objectClass: top objectClass: group cn: Pre-Windows 2000 Compatible Access description: A backward compatibility group which allows read access on all us ers and groups in the domain member: CN=S-1-5-11,CN=ForeignSecurityPrincipals,DC=schein,DC=local instanceType: 4 whenCreated: 20180701092038.0Z whenChanged: 20180701092038.0Z uSNCreated: 3572 uSNChanged: 3572 name: Pre-Windows 2000 Compatible Access objectGUID: 4c5bc5e2-a98a-467a-b427-5aff5aa71a4a objectSid: S-1-5-32-554 sAMAccountName: Pre-Windows 2000 Compatible Access sAMAccountType: 536870912 systemFlags: -1946157056 groupType: -2147483643 objectCategory: CN=Group,CN=Schema,CN=Configuration,DC=schein,DC=local isCriticalSystemObject: TRUE distinguishedName: CN=Pre-Windows 2000 Compatible Access,CN=Builtin,DC=schein,DC=local So what is missing here?
Bug #53306 is the same - but regarding error handling.
I will mark this as duplicate of Bug #53306 - please execute the script again with the latest version when Bug #53306 is released and create a new bug report. *** This bug has been marked as a duplicate of bug 53306 ***