Univention Bugzilla – Bug 43226
Starting exam fails with heavy load on DC Master
Last modified: 2023-06-12 15:39:42 CEST
Execution of command 'schoolexam/exam/start' has failed: Traceback (most recent call last): File "%PY2.7%/notifier/threads.py", line 82, in _run tmp = self._function() File "%PY2.7%/univention/management/console/modules/schoolexam/__init__.py", line 342, in _thread room=request.options['room'], File "%PY2.7%/univention/lib/umc_connection.py", line 143, in request raise HTTPException(error_message) HTTPException: 500 on localhost (computerroom/room/acquire): {"status": 511, "message": "Connection to module process failed"}
Version: 4.2-2 errata198 (Lesum) - UCS@school 4.2 v3 Die Ausführung des Kommandos schoolexam/exam/start ist fehlgeschlagen: Traceback (most recent call last): File "%PY2.7%/notifier/threads.py", line 82, in _run tmp = self._function() File "%PY2.7%/univention/management/console/modules/schoolexam/__init__.py", line 352, in _thread room=request.options['room'], File "%PY2.7%/univention/lib/umc.py", line 272, in umc_command return self.request('POST', 'command/%s' % (path,), data, headers) File "%PY2.7%/univention/lib/umc.py", line 297, in request return self.send(request) File "%PY2.7%/univention/lib/umc.py", line 316, in send raise HTTPError(request, response, self.hostname) HTTPError: 511 on slave81.school8.local (command/computerroom/room/acquire): {"status": 511, "message": "Connection to module process failed", "location": "https://slave81.school8.local/univention/command"} Role: domaincontroller_slave
Reported again: Version: 4.3-0 errata12 (Neustadt) - UCS@school 4.3 v2 Remark: hmmm, das testsystem hat einen anderen hostnamen-alias. Ich probiers nochmal mit dem anderen Namen aus. Remark: [s. voriger Fehler von vor 10m) Hm,... also, ne, geht auch nicht mit dem echten Hostnamen. Ich hab' fuers Testsystem halt auch keine echten Klassenrechner mit italk usw. Internal server error during "schoolexam/exam/start". Request: schoolexam/exam/start Traceback (most recent call last): File "%PY2.7%/notifier/threads.py", line 82, in _run tmp = self._function() File "%PY2.7%/univention/management/console/modules/schoolexam/__init__.py", line 357, in _thread room=request.options['room'], File "%PY2.7%/univention/lib/umc.py", line 272, in umc_command return self.request('POST', 'command/%s' % (path,), data, headers) File "%PY2.7%/univention/lib/umc.py", line 297, in request return self.send(request) File "%PY2.7%/univention/lib/umc.py", line 316, in send raise HTTPError(request, response, self.hostname) HTTPError: 511 on **** (command/computerroom/room/acquire): {"status": 511, "message": "Connection to module process failed", "traceback": null, "location": "https://****/univention/command"}
(In reply to Johannes Keiser from comment #2) > Reported again: > Version: 4.3-0 errata12 (Neustadt) - UCS@school 4.3 v2 > > Remark: hmmm, das testsystem hat einen anderen hostnamen-alias. Ich > probiers nochmal mit dem anderen Namen aus. > > Remark: [s. voriger Fehler von vor 10m) > Hm,... also, ne, geht auch nicht mit dem echten Hostnamen. Ich hab' fuers > Testsystem halt auch keine echten Klassenrechner mit italk usw. > > Internal server error during "schoolexam/exam/start". > Request: schoolexam/exam/start > > Traceback (most recent call last): > File "%PY2.7%/notifier/threads.py", line 82, in _run > tmp = self._function() > File > "%PY2.7%/univention/management/console/modules/schoolexam/__init__.py", line > 357, in _thread > room=request.options['room'], > File "%PY2.7%/univention/lib/umc.py", line 272, in umc_command > return self.request('POST', 'command/%s' % (path,), data, headers) > File "%PY2.7%/univention/lib/umc.py", line 297, in request > return self.send(request) > File "%PY2.7%/univention/lib/umc.py", line 316, in send > raise HTTPError(request, response, self.hostname) > HTTPError: 511 on **** (command/computerroom/room/acquire): {"status": 511, > "message": "Connection to module process failed", "traceback": null, > "location": "https://****/univention/command"} Remark: noch als Nachtrag zu dem Fehler/Problem: die exam-user bleiben im System erhalten und werden nicht nach der Klausurperiode wieder entfernt. Fuer mein Testen (ich teste die Integration/User-sync mit einem anderen System) ist das auch in Ordnung, aber ich denke, dass es im Normalbetrieb nicht das gewuenschte Verhalten im Fehlerfall ist.
This issue has been filled against UCS@school 4.1 (R2). The maintenance with bug and security fixes for UCS@school 4.1 (R2) has ended on 5th of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3 (or later). 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.