Bug 31213 – UMC "stalls" under higher load (in UCS@school computerroom)

Bug 31213 - UMC "stalls" under higher load (in UCS@school computerroom)


Summary:	UMC "stalls" under higher load (in UCS@school computerroom)

Status:	RESOLVED DUPLICATE of bug 27534

Product:	UCS@school
Classification:	Unclassified
Component:	UMC - Computer room
Version:	UCS@school 3.1
Hardware:	Other Linux

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Bugzilla Mailingliste
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-04-26 14:03 CEST by Ingo Steuwer
Modified:	2013-11-20 10:01 CET (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
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
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 Ingo Steuwer

2013-04-26 14:03:11 CEST

A customer reported that the UMC process needs to be restarted frequently while using the "computerroom" UMC module of UCS@school. The whole UMC stopps responding, both in existing sessions as in new login attemps.

Comment 1 Stefan Gohmann

2013-04-29 14:53:45 CEST

@Ingo, could you send Alex the logfiles?

Comment 2 Ingo Steuwer

2013-04-29 17:13:29 CEST

Attached to Ticket 2013042521001328 you'll find an customer generated support archive where the problem occured on 2013/04/25 between 13:00 and 14:00.

Comment 3 Alexander Kläser

2013-05-03 15:32:14 CEST

As the UMC debug level is set to 2, command request etc. are not visible in the logs. The only thing that can be clearly seen is that the computer room module is being restarted several times during a short period between 13h and 14h on the mentioned date. This is probably due to the process dying unintentionally. 

Therefore I would suggest that this bug is a duplicate of Bug 27534. Note that this problem has also been fixed in the latest UCS@school rev1 update
(Bug 31036).

*** This bug has been marked as a duplicate of bug 27534 ***