Bug 30514 – lock for computerroom does not get released

Bug 30514 - lock for computerroom does not get released


Summary:	lock for computerroom does not get released

Status:	CLOSED FIXED

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

Importance:	P1 normal (vote)
Target Milestone:	UCS@school 3.1 R2
Assigned To:	Florian Best
QA Contact:	Felix Botner

URL:
Keywords:	interim-2

Duplicates:	31178 (view as bug list)
Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-02-20 13:35 CET by Florian Best
Modified:	2013-06-07 21:38 CEST (History)
CC List:	3 users (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 Florian Best

2013-02-20 13:35:58 CET

A customer had the problem that the lock for the computerroom module was not released after several days.

Comment 1 Florian Best

2013-03-28 09:32:48 CET

The only way i could reproduce this was to "kill -9 $PID_of_computerroom_module" when the teacher already left the computerroom module. Otherwise a update-request will immediately start a new process (which would release the lock after quiting).

So this probably was caused due to a crash of the computerroom module (we had such cases caused by italc!?) when the teacher closed the computerroom module or selected another room in that moment.

Comment 2 Florian Best

2013-04-04 09:35:25 CEST

The behavior was adapted to also write the process id of the umc computerroom module to the lockfile. If the pid does not run or is not an computerroom module process the lockfile will be overwritten by the new room owner.

Comment 3 Alexander Kläser

2013-04-25 07:55:57 CEST

*** Bug 31178 has been marked as a duplicate of this bug. ***

Comment 4 Felix Botner

2013-05-23 11:19:30 CEST

OK - not able to reproduce this behavior (even with "kill -9 $PID_of_computerroom_module")

OK - PID is written to lock file 

OK - changelog

Comment 5 Sönke Schwardt-Krummrich

2013-06-07 21:38:42 CEST

UCS@school 3.1 R2 has been released:
http://download.univention.de/doc/release-notes-ucsschool-3.1-rev2.pdf

If this error occurs again, please use "Clone This Bug".