Univention Bugzilla – Bug 42318
Listener tries to connect to host=ds1 during join
Last modified: 2019-02-04 11:21:19 CET
Ticket#2016090821000374 > 08.09.16 08:39:50.338 LISTENER ( WARN ) : initializing module faillog > 08.09.16 08:40:08.057 LISTENER ( WARN ) : finished initializing module faillog with rv=0 > 08.09.16 08:40:08.057 LISTENER ( WARN ) : initializing module quota > UNIVENTION_DEBUG_BEGIN : uldap.__open host=ds1 port=7389 base=dc=example,dc=org > UNIVENTION_DEBUG_END : uldap.__open host=ds1 port=7389 base=dc=example,dc=org > UNIVENTION_DEBUG_BEGIN : uldap.__open host=ucs01.foo.bar.baz port=7389 base=dc=example,dc=org > UNIVENTION_DEBUG_END : uldap.__open host=ucs01.foo.bar.baz port=7389 base=dc=example,dc=org > UNIVENTION_DEBUG_BEGIN : uldap.__open host=ds1 port=7389 base=dc=example,dc=org > UNIVENTION_DEBUG_END : uldap.__open host=ds1 port=7389 base=dc=example,dc=org > UNIVENTION_DEBUG_BEGIN : uldap.__open host=ucs01.foo.bar.baz port=7389 base=dc=example,dc=org > UNIVENTION_DEBUG_END : uldap.__open host=ucs01.foo.bar.baz port=7389 base=dc=example,dc=org I don't think this is harmful, but it's obviously confusing - there is no "ds1" in the customer environment. I found this in univention-base-files.postinst: > univention-config-registry set ... > ldap/server/name?ds1 The customer experienced it with UCS 4.1-0, but the code is also present in 4.1-3. Procedure was: - installed UCS with role UCS Memberserver - did not join during installation - executed 'univention-join' manually
There is a Customer ID set so I set the flag "Enterprise Customer affected".
With 4.2-1 PXE installation and a join afterwards the problem still exist :-(
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. 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.
(In reply to Stefan Gohmann from comment #3) > This issue has been filled against UCS 4.1. The maintenance with bug and > security fixes for UCS 4.1 has ended on 5st of April 2018. > > Customers still on UCS 4.1 are encouraged to update to UCS 4.3. 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. The issue occurs in 4.2 as you can see from Comment 2. So please adjust the Version Number as well as the Ticket Number.