Univention Bugzilla – Bug 30044
S4 Connector UDM to Samba4 account sync delayed for about 20 min in VMWare Image
Last modified: 2013-03-25 19:57:20 CET
Found while testing VMWare Image (Bug#29885). Joining a Windows machine (Windows said, it was successful) did not add a Windows Computer in UDM. A user added in UDM was not found with univention-s4search: root@master:~$ univention-s4search cn=user1 [...] # returned 3 records # 0 entries # 3 referrals root@master:~# univention-ldapsearch -LLL uid=user1 dn: uid=user1,cn=users,dc=vm-dirk,dc=test [...] The problem was solved after manually restarting univention-s4-connector. Maybe a timing problem?
/var/log/univention/connector-s4* would be required in this case. One could check that manual modification of an S4-object (e.g. description of some samAccount) is replicated after about connector/s4/poll/sleep seconds. Additionally one could check if strace of the univention-s4-connector process shows any sign of activity.
I added a user in another VM on my local computer. Everything synced fine. I will try it once more with VMWareServer on leksvik.
I can reproduce this behaviour on leksvik-machines. I will attach both logs. These lines could be interesting: sonnector-s4.log: 16.01.2013 19:24:06,445 LDAP (PROCESS): sync to ucs: [ container] [ add] CN=Machine,cn={6ac1786c-016f-11d2-945f-00c04fb984f9},cn=policies,cn=system,dc=vm-dirk,dc=test 16.01.2013 19:24:06,469 LDAP (ERROR ): Unknown Exception during sync_to_ucs 16.01.2013 19:24:06,477 LDAP (ERROR ): Traceback (most recent call last): File "/usr/lib/pymodules/python2.6/univention/s4connector/__init__.py", line 1293, 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 1166, 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 331, in create return self._create() File "/usr/lib/pymodules/python2.6/univention/admin/handlers/__init__.py", line 702, in _create self.lo.add(self.dn, al) File "/usr/lib/pymodules/python2.6/univention/admin/uldap.py", line 387, in add raise univention.admin.uexceptions.ldapError, _err2str(msg) ldapError: No such object 16.01.2013 19:24:06,477 LDAP (WARNING): sync to ucs was not successfull, save rejected 16.01.2013 19:24:06,477 LDAP (WARNING): object was: CN=Machine,CN={6AC1786C-016F-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=vm-dirk,DC=test AND: 16.01.2013 19:24:31,924 LDAP (PROCESS): sync to ucs: [ user] [ modify] uid=dns-master,cn=users,dc=vm-dirk,dc=test 16.01.2013 19:46:55,474 MAIN (------ ): DEBUG_INIT Seems to be okay now. After 20 minutes! A second user was synced immediately (added after the first one was synced eventually). s4-connector-status.log: -------------------------------------- try to sync 3 changes from S4 done: <EOF> After these 20 minutes: -------------------------------------- try to sync 3 changes from S4 done: (1) (2) (3) Changes from S4: 0 (0 saved rejected) -------------------------------------- - sleep 5 seconds (4/10 until resync) -
Created attachment 4986 [details] connector-s4.log
Created attachment 4987 [details] connector-s4-status.log
The GPO-container related traceback (CN=Machine,cn={6ac1786c-016f-11d2-945f-00c04fb984f9},cn=policies,cn=system) ist a cosmetic issue (Bug 27293). Reconfirmed details about the logs attached: * User jhuller was created at about 19:3x in UDM * Log entries indicate a non-manual restart of the S4 connector at 19:46:55,474 * The user account is replicated ti Samba 4 at 19:46:55,683 *
* The issue seems to be specific for machines hosted on the specific virtualization server and did not occur on a VM hosted locally on a notebook
I can reproduce it if I change the IP address. For the current VMware image we have a workaround, see Bug #29885. This bug should be solved for UCS 3.1-1, maybe there is only a s4connector restart missing while changing the IP address in system.
*** This bug has been marked as a duplicate of bug 30119 ***
Verified: * Fix for Bug #30119 is in ucs3.1-1
UCS 3.1-1 has been released: http://download.univention.de/doc/release-notes-3.1-1_en.pdf http://download.univention.de/doc/release-notes-3.1-1.pdf If this error occurs again, please use "Clone This Bug".