Bug 44076 – Error 502 while running the school installer

Bug 44076 - Error 502 while running the school installer


Summary:	Error 502 while running the school installer

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC (Generic)
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:	UMC maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-03-26 18:39 CEST by Stefan Gohmann
Modified:	2020-07-03 20:53 CEST (History)
CC List:	2 users (show)

See Also:	39538 31432
What kind of report is it?:	Bug Report
What type of bug is this?:	6: Setup Problem: Issue for the setup process
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	3: A User would likely not purchase the product
User Pain:	0.206
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
umc-school-installer-502.png (65.73 KB, image/png) 2017-03-26 18:39 CEST, Stefan Gohmann	Details
USI of the system (149.66 KB, application/x-bzip) 2017-03-26 18:43 CEST, Stefan Gohmann	Details
journalctl.log.bz2 (72.46 KB, application/x-bzip) 2017-03-26 18:44 CEST, Stefan Gohmann	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Stefan Gohmann

2017-03-26 18:39:36 CEST

Created attachment 8648 [details]
umc-school-installer-502.png

I got a 502 error while running the school installer.

It doesn't look like the problem in Bug #44052:
root@master421:~# ls -la /var/run/umc-*
-rw------- 1 root root 5 Mär 25 14:13 /var/run/umc-server.pid
-rw------- 2 root root 0 Mär 25 14:13 /var/run/umc-server.pid.lock
-rw------- 1 root root 5 Mär 25 14:13 /var/run/umc-web-server.pid
-rw------- 2 root root 0 Mär 25 14:13 /var/run/umc-web-server.pid.lock
root@master421:~# ps -ef | grep -i management-console
root      1352     1  0 Mär25 ?       00:00:45 /usr/bin/python2.7 /usr/sbin/univention-management-console-server start
root      1697     1  0 Mär25 ?       00:06:24 /usr/bin/python2.7 /usr/sbin/univention-management-console-web-server start
root      9781  1352  0 18:33 ?        00:00:02 /usr/bin/python2.7 /usr/sbin/univention-management-console-module -m schoolinstaller -s /var/run/univention-management-console/1352-1490545999499.socket -d 2 -l de_DE.UTF-8
root     10082 10059  0 18:38 pts/0    00:00:00 grep -i management-console
root@master421:~#

Comment 1 Florian Best

2017-03-26 18:41:41 CEST

Can you attach apache (acces+error) logs and umc (umc-server, umc-webserver, umc-module-schoolinstaller) logs?
If it's reproduible please open the network console and copy the response of the failed 502 request.

Comment 2 Stefan Gohmann

2017-03-26 18:43:43 CEST

Created attachment 8649 [details]
USI of the system

Comment 3 Stefan Gohmann

2017-03-26 18:44:06 CEST

Created attachment 8650 [details]
journalctl.log.bz2

Comment 4 Stefan Gohmann

2017-03-26 18:44:37 CEST

10.201.42.1 is the test system if you want to test something.

Comment 5 Florian Best

2017-03-26 18:50:01 CEST

I don't have VPN access currently :/

Comment 6 Florian Best

2017-03-26 19:00:06 CEST

In the screenshot you see "Critical: There is no current installation running. Maybe the previous process died?".

So this is not an UCS 4.2 Issue, I saw these crashes already in UCS 4.1-3, that's why I added this debug output (instead of a forever hanging progress bar). But I can't explain what's going wrong here.

If we fix the architecture it won't happen anymore: Bug #39538

Comment 7 Stefan Gohmann

2017-03-26 20:12:39 CEST

Hm, you are right, it isn't reproducible. I'll remove the target milestone.

Comment 8 Ingo Steuwer

2020-07-03 20:53:38 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.