Univention Bugzilla – Bug 50199
[UDM HTTP API] log 503 service unavailable
Last modified: 2019-10-02 16:06:32 CEST
Nothing helpful is written to the log file, when an error on the server (HTTP 5xx) happens. I just received a "HTTP 503: Service Unavailable", but the reason is unknown. In the log file there is only: ERROR:tornado.access:503 POST /udm/users/user/ (127.0.0.1) 13680.65ms Add more informative information or tracebacks to the logfile to be able to analyse problems.
With: ucr set directory/manager/rest/debug/level='2' directory/manager/rest/show-tracebacks='yes' all errors tracebacks inclusive are logged and also part of the response. → I am changing the bug title. This specific error happens when the subprocesses are (not yet) started.
The log contains already this line: "ERROR:tornado.access:503 GET /udm/index.html (127.0.0.1) 2.15ms"
(In reply to Florian Best from comment #1) > With: ucr set directory/manager/rest/debug/level='2' > directory/manager/rest/show-tracebacks='yes' > all errors tracebacks inclusive are logged and also part of the response. > → I am changing the bug title. > > This specific error happens when the subprocesses are (not yet) started. The process were all started. No tracebacks is logged, only one line like this: ERROR:tornado.access:503 POST /udm/users/user/ (127.0.0.1) 23438.59ms I think it happens, when no subprocess of the main tornado process replies within a certain time. Happens when 100 clients connect at the same time.
The exception is now logged. univention-directory-manager-rest (9.0.15-8) 339c62621426 | Bug #50199: log exception when subprocesses are unreachable
UCS 4.4-2 has been released: https://docs.software-univention.de/release-notes-4.4-2-en.html https://docs.software-univention.de/release-notes-4.4-2-de.html If this error occurs again, please use "Clone This Bug".