Had to run Join scripts immediately after upgrade to 4.4 from 4.3. I am getting the following errors below on the appcenter and radius join scripts.
RUNNING 30univention-appcenter.inst
2019-04-20 23:29:40.566672017-06:00 (in joinscript_init)
Object exists: cn=apps,cn=univention,dc=skaggscatholiccenter,dc=org
Object exists: cn=ldapschema,cn=univention,dc=skaggscatholiccenter,dc=org
INFO: No change of core data of object univention-app.
Object exists: cn=ldapacl,cn=univention,dc=skaggscatholiccenter,dc=org
INFO: No change of core data of object 66univention-appcenter_app.
Object exists: cn=udm_syntax,cn=univention,dc=skaggscatholiccenter,dc=org
INFO: No change of core data of object app_syntax.
Object exists: cn=udm_module,cn=univention,dc=skaggscatholiccenter,dc=org
INFO: No change of core data of object appcenter/app.
No modification: cn=univention-app,cn=ldapschema,cn=univention,dc=skaggscatholiccenter,dc=org
No modification: cn=66univention-appcenter_app,cn=ldapacl,cn=univention,dc=skaggscatholiccenter,dc=org
No modification: cn=app_syntax,cn=udm_syntax,cn=univention,dc=skaggscatholiccenter,dc=org
No modification: cn=appcenter/app,cn=udm_module,cn=univention,dc=skaggscatholiccenter,dc=org
Waiting for activation of the extension object univention-app: OK
Waiting for activation of the extension object 66univention-appcenter_app: OK
Waiting for activation of the extension object app_syntax:........................................................ERROR: Master did not mark the extension object active within 180 seconds.
ERROR
ucs_registerLDAPExtension: registraton of /usr/share/univention-appcenter/app_syntax.py failed.
EXITCODE=1
cadb298d-3454-46df-8587-3a64de9e6f67
AND
RUNNING 80univention-radius.inst
2019-04-20 23:32:43.769189977-06:00 (in joinscript_init)
Object exists: cn=services,cn=univention,dc=skaggscatholiccenter,dc=org
Object exists: cn=RADIUS,cn=services,cn=univention,dc=skaggscatholiccenter,dc=org
WARNING: cannot append RADIUS to service, value exists
No modification: cn=ad,cn=dc,cn=computers,dc=skaggscatholiccenter,dc=org
Generating DH parameters, 1024 bit long safe prime, generator 2
This is going to take a long time
.......................................................................................+.......+........................................+....................................+...+...............................................................+...................................................................................................................................................................................................................+.................................+.......++*++*++*++*++*
unable to write 'random state'
Object exists: cn=ldapschema,cn=univention,dc=skaggscatholiccenter,dc=org
INFO: No change of core data of object networkaccess.
Object exists: cn=ldapacl,cn=univention,dc=skaggscatholiccenter,dc=org
INFO: No change of core data of object 59univention-radius.
INFO: No change of core data of object 66univention-radius.
No modification: cn=networkaccess,cn=ldapschema,cn=univention,dc=skaggscatholiccenter,dc=org
No modification: cn=59univention-radius,cn=ldapacl,cn=univention,dc=skaggscatholiccenter,dc=org
No modification: cn=66univention-radius,cn=ldapacl,cn=univention,dc=skaggscatholiccenter,dc=org
Waiting for activation of the extension object networkaccess:........................................................ERROR: Master did not mark the extension object active within 180 seconds.
ERROR
ucs_registerLDAPExtension: registraton of /usr/share/univention-radius/networkaccess.schema failed.
EXITCODE=1
b25a725a-6bba-49f4-804f-8572f9c3a294
I don’t know why on the domain master it would say the connection is refused. I couldn’t find out how to resolve this specifically, it was mentioned in the thread that I should reset the listener cache in the “solution” Troubleshooting: Listener-/Notifier
From /var/lib/univention-ldap/notify/transaction I see this.
27301721 dc=skaggscatholiccenter,dc=org m
27301722 dc=skaggscatholiccenter,dc=org m
27301723 dc=skaggscatholiccenter,dc=org m
27301724 dc=skaggscatholiccenter,dc=org m
27301725 dc=skaggscatholiccenter,dc=org m
27301726 dc=skaggscatholiccenter,dc=org m
27301727 dc=skaggscatholiccenter,dc=org m
Listener state is run but it’s log is showing this:
I also noticed it’s bind dn is cn=admin instead of cn=administrator
23.04.19 13:55:58.115 LISTENER ( WARN ) : Notifier/LDAP server is ad.skaggscatholiccenter.org:7389
23.04.19 13:55:58.115 LDAP ( PROCESS ) : connecting to ldap://ad.skaggscatholiccenter.org:7389
23.04.19 13:55:58.119 LDAP ( INFO ) : simple_bind as cn=admin,dc=skaggscatholiccenter,dc=org
23.04.19 13:55:58.120 LISTENER ( INFO ) : connecting to notifier ad.skaggscatholiccenter.org:6669
23.04.19 13:55:58.120 LISTENER ( INFO ) : connection to 172.16.0.9 failed with errorcode 111: Connection refused
23.04.19 13:55:58.120 LISTENER ( ERROR ) : failed to connect to any notifier
23.04.19 13:55:58.120 LISTENER ( WARN ) : can not connect any server, retrying in 30 seconds
23.04.19 13:56:28.120 LISTENER ( WARN ) : Notifier/LDAP server is ad.skaggscatholiccenter.org:7389
23.04.19 13:56:28.120 LDAP ( PROCESS ) : connecting to ldap://ad.skaggscatholiccenter.org:7389
23.04.19 13:56:28.124 LDAP ( INFO ) : simple_bind as cn=admin,dc=skaggscatholiccenter,dc=org
23.04.19 13:56:28.124 LISTENER ( INFO ) : connecting to notifier ad.skaggscatholiccenter.org:6669
23.04.19 13:56:28.124 LISTENER ( INFO ) : connection to 172.16.0.9 failed with errorcode 111: Connection refused
23.04.19 13:56:28.124 LISTENER ( ERROR ) : failed to connect to any notifier
23.04.19 13:56:28.124 LISTENER ( WARN ) : can not connect any server, retrying in 30 seconds
The Notifier state is finish and it’s log is showing this:
Hi,
so your issue is with the notifier.
The log you posted is not where the notifier tries to start. When you attempt to start with systemctl start univention-directory-notifier you will see a line as shown with the current time stamp of the start command:
Christian, I searched the log file and it does not contain “DEBUG”. I moved the log file so it would create a new one and repeated the procedure and it does not contain debug at all. It is still exactly as I posted above.
# killall univention-directory-notifier
univention-directory-notifier: no process found
# killall -9 univention-directory-notifier
univention-directory-notifier: no process found
# ucr get notifier/autostart
yes
# systemctl enable univention-directory-notifier
univention-directory-notifier.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable univention-directory-notifier
“killed by” is a sign of failure. Some lines above your see again a “failed” and below “TRANSFILE”.
And on the top of my quote you see a successful write command: write(3, "25.04.19 07:37:51.221 TRANSFILE"..., 65) = 65
where it has written successful (!) 65bytes to the file with the file descriptor 3. Which is: