Univention Bugzilla – Bug 48822
Listener initialization doesn't abort in case notifier connection terminates
Last modified: 2019-02-28 18:09:23 CET
Created attachment 9878 [details] abort_if_change_update_schema_failed.patch When the notifier is restarted while the listener is initializing the modules, the listener logs: ================================================== 28.02.19 11:54:51.750 LISTENER ( INFO ) : initialize schema for module SOME-MODULE [...] 28.02.19 11:54:51.966 LISTENER ( INFO ) : module SOME-MODULE for relating objects 28.02.19 11:54:52.268 LISTENER ( ALL ) : >>>MSGID: 123 GET_SCHEMA_ID 28.02.19 11:54:52.268 LISTENER ( ALL ) : RESULT: [(null)] 28.02.19 11:54:52.268 LISTENER ( ERROR ) : connection to notifier was closed 28.02.19 11:54:52.268 LISTENER ( ERROR ) : failed to get schema DN 28.02.19 11:54:52.268 LISTENER ( WARN ) : finished initializing module SOME-MODULE with rv=80 28.02.19 11:54:52.269 LISTENER ( WARN ) : initializing module NEXT-MODULE ================================================== The listener should not continue initializing modules if it failed to read from the notifier. See attached patch proposal.