Univention Bugzilla – Bug 39934
98univention-samba4slavepdc-dns.inst fails in large environment
Last modified: 2015-11-18 09:27:24 CET
After creating a big UCS environment (using the scripts in ucs-test-tools: /usr/sbin/import_ldif_with_listener /usr/share/ucs-test-tools/customer5000.ldif) the joinscript fails during the installation of a UCS@school singlemaster. RUNNING 98univention-samba4slavepdc-dns.inst 2015-11-12 17:02:01.783797442+01:00 (in joinscript_init) response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful response to GSS-TSIG query was unsuccessful Failed update of 24 entries EXITCODE=24
The joinscript 97univention-s4-connector.inst fails, too. Maybe this works if Bug #39933 is fixed?
> response to GSS-TSIG query was unsuccessful Says that Kerberized DDNS update failed, so the Kerberos setup would need to be checked. In UCS@school we override the S4-Connector replication of some of the DNS SRV records. If this only occurs in large environments it might indicate a timing issue there. Wel'll have to analyse a system in this state.
It should be fixed with Bug #39959. *** This bug has been marked as a duplicate of bug 39959 ***