Univention Bugzilla – Bug 33426
UMC server crashes upon login if it is not restarted after the update
Last modified: 2023-03-25 06:43:28 CET
Following scenario: * Update to 3.2 is launched in UMC module * User session is timed out * Upon re-login, the UMC server crashes
An UMC server update has been added to the end of the updater process. univention-updater (9.0.36-1) unstable; urgency=low . * Bug #33426: restart UMC server after update
UMC shows a popup that the relogin is tried, but it does not work. The popup also describe that a simple relogin would be possible at a later point and that works in my tests. A simple F5 shows the login dialog and everything works fine.
I've added a redirection for the status messages, otherwise: Starting update process, this may take a while. Check /var/log/univention/updater.log for more information. Running postup.sh script:Restart UMC server components to finish update... restart done done. Checking for release updates: none Checking for package updates: none
Login dialogue does not re-appear upon UMC restart → REOPENED
(In reply to Alexander Kläser from comment #4) > Login dialogue does not re-appear upon UMC restart → REOPENED The problem occurs due to incorrect status code handling → Bug 33443 As workaround, the following hint is printed into the log file: **************************************************** * THE UPDATE HAS BEEN FINISHED SUCCESSFULLY. * * Please make a page reload of UMC and login again * ****************************************************
I also added a "sleep 10s" before restarting the UMC server. This is to make sure that this note in the updater.log has being transmitted to the client. (Note that the update is running via an at-job.)
(In reply to Alexander Kläser from comment #5) > (In reply to Alexander Kläser from comment #4) > > Login dialogue does not re-appear upon UMC restart → REOPENED > > The problem occurs due to incorrect status code handling → Bug 33443 > > As workaround, the following hint is printed into the log file: > > **************************************************** > * THE UPDATE HAS BEEN FINISHED SUCCESSFULLY. * > * Please make a page reload of UMC and login again * > **************************************************** That message is now displayed.
(In reply to Moritz Muehlenhoff from comment #7) > (In reply to Alexander Kläser from comment #5) > > (In reply to Alexander Kläser from comment #4) > > > Login dialogue does not re-appear upon UMC restart → REOPENED > > > > The problem occurs due to incorrect status code handling → Bug 33443 > > > > As workaround, the following hint is printed into the log file: > > > > **************************************************** > > * THE UPDATE HAS BEEN FINISHED SUCCESSFULLY. * > > * Please make a page reload of UMC and login again * > > **************************************************** > > That message is now displayed. Hmm, but only via CLI update. I don't see this message in the UMC module. Please modify the postup.sh script on the download server. The PGP signature must also be re-generated.
The following change has been made in r46121: =================================================================== --- script/postup.sh (Revision 46120) +++ script/postup.sh (Arbeitskopie) @@ -160,7 +160,7 @@ **************************************************** -" +" >>"$UPDATER_LOG" 2>&1 echo -n "Restart UMC server components to finish update... " >>"$UPDATER_LOG" 2>&1 sleep 10s =================================================================== postup.sh + updated signature have been uploaded to testing.univention.de and copied to the 3.2 path (without update_mirror.sh). Tests for testing.univention.de were ok.
I have not yet called updated_mirror.sh.
(In reply to Alexander Kläser from comment #10) > I have not yet called updated_mirror.sh. OK