Univention Bugzilla – Bug 42865
Session timeout during system setup after successful installation
Last modified: 2019-01-03 07:19:04 CET
version/erratalevel: 324 version/patchlevel: 3 version/version: 4.1 During a technical training, 4 out of 8 newly installed UCS Master VMs hit a UMC timeout during system setup. We left for lunch while the system setup was still busy installing the previously selected software components (Samba/AD, DHCP Server). After we came back (about 1 hour later), half of the VMs were locked (see attached screenshot). Unfortunately we don't know the password of the user __systemsetup__ Rebooting the systems via an ACPI event seems to be a valid workaround, we did not experience any drawbacks so far.
Created attachment 8201 [details] Screenshot of locked system setup session
Which installation media was used to install UCS?
*** Bug 42870 has been marked as a duplicate of this bug. ***
Also reported via feedback, from Bug #42870: (In reply to Stefan Gohmann from comment #0) > Feedback Ticket #2016103121000756: > > FEEDBACK: Perhaps left it too long configuring. > > When i came back, the background said configuration successful, but ontop of > that was an error message box which I could not read because ontop of that > was the UCS login screen > with the user set to "_systemsetup_" of which the password i set earlier did > not work. > > i tried a few other user names, like admin, root etc. i now realise the user > is administrator and perhaps that would have worked. instead i had to reboot > it. all seems fine now...
I could not reproduce the issue with the most recent 4.1-3 DVD and the 4.1-4 ucs appliance. Setup.log and dpkg.log of affected systems might help to analyse this further. I suspect that system-setup-boot was updated during the setup process, and our previous errata updates to uss-boot do not catch all possible cases that might produce such an error.
What probably more helps is where did you get the installation media from? Which initial system setup version has this been. (Did you select "update system after installation"? Because then your "version/erratalevel: 324" is not the installation version). @Erik I had this issue, too, with our internal UCS 4.1-3 USB stick on a hardware system. But this was due to http://errata.software-univention.de/ucs/4.1/244.html.
Created attachment 8204 [details] dpkg.log (In reply to Florian Best from comment #6) > What probably more helps is where did you get the installation media from? I used: > mgrandje@utby:~$ ls -la /mnt/omar/vmwares/kvm/iso/ucs/UCS_4.1-3-amd64.iso > -rw-rw-r--+ 1 edamrose Domain Users 1279492096 Aug 17 16:48 /mnt/omar/vmwares/kvm/iso/ucs/UCS_4.1-3-amd64.iso > mgrandje@utby:~$ md5sum /mnt/omar/vmwares/kvm/iso/ucs/UCS_4.1-3-amd64.iso > 513d2fab9d77ab49243baa1fdbbe13db /mnt/omar/vmwares/kvm/iso/ucs/UCS_4.1-3-amd64.iso > Which initial system setup version has this been. (Did you select "update > system after installation"? Because then your "version/erratalevel: 324" is > not the installation version). Yes, I did select "update system after installation". > root@ucs-6361:~# rgrep "install univention-system-setup" /var/log/dpkg.log > 2016-11-07 11:33:39 install univention-system-setup:all <none> 9.0.4-35.979.201608091120 > 2016-11-07 11:33:39 install univention-system-setup-boot:all <none> 9.0.4-35.979.201608091120 I attached dpkg.log and setup.log If further infos are needed, VM runs on utby (mgrandje_ucs41-64-121, 10.200.30.121), feel free. I also experienced Bug #42550, but did not notice this yesterday - not sure if this is related.
Created attachment 8205 [details] setup.log
Please also attach management-console-module-setup.log
Created attachment 8206 [details] management-console-module-setup.log
So, system-setup-boot is starting with 9.0.4-35 (which was never released). This is a version between http://errata.software-univention.de/ucs/4.1/234.html (9.0.4-33) and http://errata.software-univention.de/ucs/4.1/238.html (9.0.4-36). During the installation it upgrades system-setup-boot to 9.0.4-48. which is http://errata.software-univention.de/ucs/4.1/278.html (including errata 292, 244).
The file you used seems to be a test DVD i copied to our internal VM environment. I forgot to update the iso with the final version, for which i am sorry. The tested and officially released ISO can be found at http://updates.software-univention.de/download/ucs-cds/ucs4.1-3/ or omar:/var/univention/buildsystem2/mirror/ftp/download/ucs-cds/ucs4.1-3/ Another test with UCS_4.1-3-amd64.iso (MD5: b72705313ac55325f21e81645d45b662) did not reproduce your problem. -> WORKSFORME Before resolving this bug i will try to contact the user of the feedback ticket at which a similar error occured.
Created attachment 8316 [details] Script to reproduce the installation problem (In reply to Erik Damrose from comment #12) > The file you used seems to be a test DVD i copied to our internal VM > environment. I forgot to update the iso with the final version, for which i > am sorry. > > The tested and officially released ISO can be found at > > http://updates.software-univention.de/download/ucs-cds/ucs4.1-3/ > or > omar:/var/univention/buildsystem2/mirror/ftp/download/ucs-cds/ucs4.1-3/ > > Another test with UCS_4.1-3-amd64.iso (MD5: > b72705313ac55325f21e81645d45b662) did not reproduce your problem. > > -> WORKSFORME > > Before resolving this bug i will try to contact the user of the feedback > ticket at which a similar error occured. I could reproduce the problem with /mnt/omar/vmwares/kvm/iso/ucs/UCS_4.1-3-amd64.iso. I have attached a VNC script that will reproduce the bug with a standard installation with German language settings. I also have a VM snapshot with opened JS-console. It seems that various requests were not answered after some point in the update process. A final call to setup/finished is then answered with 401. Presumably the apache service has switched off, its package has been updated too long such that the session is gone. Nevertheless, UMC should be able to recover as the password is given as query string. We could try to update first apache in the preup script and then run the rest of the updates.
I think I can recognize the problem in the piwik statistics quite often.
Could this be a duplicated of Bug 42211?
Does it still happen with UCS 4.2? If yes, we should fix it otherwise we should wait and see if it happens again with 4.1-4 or 4.2.
(In reply to Stefan Gohmann from comment #16) > Does it still happen with UCS 4.2? If yes, we should fix it otherwise we > should wait and see if it happens again with 4.1-4 or 4.2. I could not find a proper hypothesis in order to explain this behaviour. I would expect this issue not to happen with UCS 4.2. There are various things that have been improved (UMC session handling, activation process, setup wizard). So let us wait.
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.