Univention Bugzilla – Bug 55662
30univention-monitoring-client - State pending
Last modified: 2023-03-16 10:41:51 CET
After a fresh install of univention 5.0 and upgrade to the latest version 5.0-2 errata572 the domain join status of the script is pending. Retry the joins lead to timeout and do not change the status. System diag reports: "univention-check-join-status" returned a problem with the domain join. STDOUT: Warning: 'univention-monitoring-client' is not configured. Error: Not all install files configured: 1 missing See Manual: Analysis of listener/notifier problems or run the join-scripts via "Domain join" module.
Please attach the contents of /var/log/univention/join.log and /var/log/univention/listener.log (anonymized or flagged as "univentionstaff").
Created attachment 11028 [details] listener.log
Created attachment 11029 [details] join.log
just in case you are stumbling around i made a mistake during the anonymization. In listener log i replaced our domain with: "demo." mind the dot :)
Created attachment 11030 [details] join.log - after retry
Created attachment 11031 [details] listener.log - after retry
The listener.log doesn't reveal the real error. Nevertheless, please try: udm settings/ldapschema modify --dn cn=univention-monitoring,cn=ldapschema,cn=univention,dc=demo,dc=intranet --set packageversion=0 and then call the joinscript again. Does the same error happen? I don't think so. But there could be similar follow-up errors with other objects.
Script replies with: "E: Invalid syntax: packageversion: Version must not be lower than the current one." I've looked at the dn and the actual version is: 1.0.0-8A~5.0.0.202211081645
Also happening in my UCS 5.0-2 testenv, after updating to latest errata (5.0-2 e572). The joinscript ran successfully when i updated to 5.0-3
I don't see unusual behavior in the listener.log. Could be that the listener module couldn't be loaded at all due to import errors like Bug #55590 (introduced during some erratum).
I upgraded my VMs to 5.0-3 and for me it is still failing: univention-run-join-scripts --run-scripts 30univention-monitoring-client > Running 30univention-monitoring-client.inst failed (exitcode: 1) tail /var/log/univention/join.log > 2023-02-08 17:40:05.567381639+01:00 (in joinscript_init) > Object exists: cn=monitoring,dc=phahn,dc=dev > Object exists: cn=ldapschema,cn=univention,dc=phahn,dc=dev > Object exists: cn=ldapacl,cn=univention,dc=phahn,dc=dev > No modification: cn=univention-monitoring,cn=ldapschema,cn=univention,dc=phahn,dc=dev > No modification: cn=62univention-monitoring,cn=ldapacl,cn=univention,dc=phahn,dc=dev > Waiting for activation of the extension object univention-monitoring: ......INFO: No change of core data of object univention-monitoring. > INFO: No change of core data of object 62univention-monitoring. > ERROR: Primary Directory Node did not mark the extension object active within 180 seconds. > ERROR > ucs_registerLDAPExtension: registraton of /usr/lib/univention-monitoring-client/schema/univention-monitoring.schema failed. > 30univention-monitoring-client.inst: LDAP Schema/ACL > EXITCODE=1
In our context the following helped: udm settings/ldapacl remove --dn "cn=62univention-monitoring,cn=ldapacl,cn=univention,$(ucr get ldap/base)" udm settings/ldapschema remove --dn "cn=univention-monitoring,cn=ldapschema,cn=univention,dc=app,$(ucr get ldap/base)" univention-run-join-scripts --run-scripts 30univention-monitoring-client --force univention-run-join-scripts: runs all join scripts existing on local computer. copyright (c) 2001-2022 Univention GmbH, Germany Running pre-joinscripts hook(s): done Running 30univention-monitoring-client.inst done Running post-joinscripts hook(s): done Works for us under UCS 5.0-2 e610