Problem:
The ox-connector shows the following traceback
2024-10-02 10:50:39 INFO Loading old object from /var/lib/univention-appcenter/apps/ox-connector/data/listener/old/d0f129e2-0dee-103f-99d7-5575537d8c50.json
2024-10-02 10:50:39 INFO ... found 1465
2024-10-02 10:50:39 INFO Error while processing /var/lib/univention-appcenter/apps/ox-connector/data/listener/2024-10-02-07-40-26-934884.json
2024-10-02 10:50:39 WARNING Traceback (most recent call last):
2024-10-02 10:50:39 WARNING File "/tmp/univention-ox-connector.listener_trigger", line 415, in run_on_files
2024-10-02 10:50:39 WARNING function(obj)
2024-10-02 10:50:39 WARNING File "/usr/lib/python3.9/site-packages/univention/ox/provisioning/__init__.py", line 108, in run
2024-10-02 10:50:39 WARNING modify_group(new_obj)
2024-10-02 10:50:39 WARNING File "/usr/lib/python3.9/site-packages/univention/ox/provisioning/groups.py", line 140, in modify_group
2024-10-02 10:50:39 WARNING group.modify()
2024-10-02 10:50:39 WARNING File "/usr/lib/python3.9/site-packages/univention/ox/soap/backend.py", line 176, in modify
2024-10-02 10:50:39 WARNING assert self.name is not None
2024-10-02 10:50:39 WARNING AssertionError
2024-10-02 10:50:39 INFO This is consecutive error #745
Investigation:
This error indicates, that something is wrong with one of the users in the group, which is synchronised.
In ox all users should be found, which are members of this group, otherwise the sync fails and you will receive this error.
Solution:
- If the user still exists in UCS Ldap you should retrigger the user, so it will be synchronised again.
DN="uid=user100,cn=users,$(ucr get ldap/base)"
ENTRY_UUID="$(univention-ldapsearch -b "$DN" + | grep entryUUID | awk '{ print $2 }')"
cat > /var/lib/univention-appcenter/listener/ox-connector/$(date +%Y-%m-%d-%H-%M-%S).json <<- EOF
{
"entry_uuid": "$ENTRY_UUID",
"dn": "$DN",
"object_type": "users/user",
"command": "modify"
}
EOF