Univention Bugzilla – Bug 54254
univention-samba4 should pull in univention-s4-connector
Last modified: 2021-12-16 19:27:06 CET
During development/support I did `apt-get install univention-samba4`, which did NOT pull in `univention-s4-connector`. `98univention-samba4-dns.inst` will then hang infinitely waiting for # tail /var/log/univention/join.log 2021-12-16 10:07:01.571661449+01:00 (in joinscript_init) Waiting for RID Pool replication: done. Object created: uid=dns-m38,cn=users,dc=qa50,dc=pmh looking for spn account "dns-m38" in local samba # apt-cache rdepends univention-s4-connector univention-s4-connector Reverse Depends: univention-management-console-module-adtakeover univention-management-console-module-adtakeover After "apt-get install univention-s4-connector" the issue "magically" resolved itself and the join script continued. Please add "Recommends: univention-s4-connector" or even a "Depends:". Alternative: Fix the join script to not required S4C to be functional and running. Also see Bug #50036
It's the other way around univention-s4-connector pulls univention-samba4. univention-app install samba4 does the right thing for you, adjusted to the server role.
(In reply to Arvid Requate from comment #1) > It's the other way around univention-s4-connector pulls univention-samba4. `98univention-samba4-dns.inst` hangs indefinitely when S4C is NOT installed → BUG → please fix this Please also add the Recommends: as those two packages seem to require each other: that is the correct way to handle this circular dependency between those two packages.
univention-samba4 requires a S4-Connector running somewhere in the domain. IIRC it checks this by looking for a corresponding univentionService advertisement. univention-s4-connector on the contrary has a direct package dependecy on univention-samba4. As such, it would be suicide to fix the bug report as filed here. Please file a better request, based on the desired outcome. And please use the intended way of installing UCS.