Univention Bugzilla – Bug 30412
notifier in appliance setup when changing from DHCP to a fixed IP addresss
Last modified: 2013-12-11 16:05:16 CET
The same problem applies to the notifier. +++ This bug was initially created as a clone of Bug #30408 +++ The same problem applies to the listener. +++ This bug was initially created as a clone of Bug #30119 +++ The s4connector is not synchronizing new LDAP entries when booting in appliance mode and configuring a master system with Samba4 + changing the DHCP IP address to a fixed static address. strace shows that the s4connector hangs while reading from a socket. The problem is reproducible with the current UCS VMware image. This behaviour is possibly due to an open LDAP connection to the old DHCP IP address that gets invalidated after system setups cleanup (which is executed as soon as the user is confirming to continue booting). A restart of the s4connector in the appliance hooks, as well as a "nscd -i hosts" does not change this behaviour.
Fixed in errata3.1-0 and ucs3.1-1. Advisory: 2013-02-13-univention-directory-notifier.yaml Changelog: changelog-3.1-1 How about adding it to /etc/network/if-up.d/ to?
OK, after booting in appliance mode and setting up a master with univention-samba4 and univention-s4-connector (and changing the DHCP IP addressto a fixed static address) the connector now synchronizes UDM Objects to samba4. OK - errata3.1-0 OK - ucs3.1-1 OK - Advisory OK - Changelog
http://errata.univention.de/3.1-errata47.html