Univention Bugzilla – Bug 27293
Vorübergehende tracebacks im S4 Connector bei Anlegen von GPO vom Client aus
Last modified: 2019-02-05 21:50:08 CET
Nach Anlegen einer GPO vom Windows Client aus erscheinen folgende Tracebacks im connector-s4.log. Die Rejects für die CN=User und CN=Manchine Container unterhalb des msgpo-Objekts sind nur vorübergehend, weil das parent-Objekt noch nicht angelegt ist. Ggf. kann man hier die Replikationsreihenfolge optimieren: ========================================================================== 21.05.2012 22:20:20,616 LDAP (PROCESS): sync to ucs: [ container] [ add] CN=User,cn={4e12c941-6632-4aa8-97d7-874368319119},cn=policies,cn=system,dc=nos4,dc=local 21.05.2012 22:20:20,677 LDAP (ERROR ): Unknown Exception during sync_to_ucs 21.05.2012 22:20:20,677 LDAP (ERROR ): Unknown Exception during sync_to_ucs 21.05.2012 22:20:20,678 LDAP (ERROR ): Traceback (most recent call last): File "/usr/lib/pymodules/python2.6/univention/s4connector/__init__.py", line 1283, in sync_to_ucs result = self.add_in_ucs(property_type, object, module, position) File "/usr/lib/pymodules/python2.6/univention/s4connector/__init__.py", line 1159, in add_in_ucs return ucs_object.create() and self.__modify_custom_attributes(property_type, object, ucs_object, module, position) File "/usr/lib/pymodules/python2.6/univention/admin/handlers/__init__.py", line 332, in create return self._create() File "/usr/lib/pymodules/python2.6/univention/admin/handlers/__init__.py", line 701, in _create self.lo.add(self.dn, al) File "/usr/lib/pymodules/python2.6/univention/admin/uldap.py", line 364, in add raise univention.admin.uexceptions.ldapError, _err2str(msg) ldapError: No such object ==========================================================================
There is a Customer ID set so I set the flag "School Customer affected".
This issue has been filled against UCS@school 3. The maintenance with bug and security fixes for the last UCS@school version for UCS 3.x (→ UCS@school 3.2) has ended on Dec 31, 2016. Customers still on UCS 3.x are encouraged to update to UCS 4.3 (or later). Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.