When an exception is raised (in ucs-school-umc-installer/umc/python/schoolinstaller/__init__.py:532) the UMC server logs the message of the exception (to management-console-module-schoolinstaller.log) with level PROCESS. Searching the logfile for "error" or "fail" does not yield a hit. Log exceptions with loglevel ERROR.
All tracebacks which are send to the frontend are logged in /var/log/univention/management-console-web-server.log.
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.
* Stacktraces are now logged with ERROR facility instead of PROCESS * Stacktraces are now again correctly formatted (a tuple was logged which made all newlines appear as \n) * Stacktraces are now logged in both /var/log/univention/management-console-server.log and /var/log/univention/management-console-module-$MDOULEID.log (and therefore twice in Nubus, as these files are just "stdout" there) univention-management-console.yaml 866254189f2c | feat(umc): log exception stacktraces more explicitly univention-management-console (14.0.47) 866254189f2c | feat(umc): log exception stacktraces more explicitly
errata-yaml ok code-review ok log messages ok packagebuild ok problem reproduced ok fix reproduced ok
<https://errata.software-univention.de/#/?erratum=5.2x60>