From ce4ec96c3b01d751fb9d057c5592b3f3a31e5968 Mon Sep 17 00:00:00 2001 From: Graham Dumpleton Date: Fri, 13 Sep 2024 14:46:37 +1000 Subject: [PATCH] Add docs note about stack traces when using request timeout. --- docs/configuration-directives/WSGIDaemonProcess.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/configuration-directives/WSGIDaemonProcess.rst b/docs/configuration-directives/WSGIDaemonProcess.rst index 4a76019a..ec1bebb3 100644 --- a/docs/configuration-directives/WSGIDaemonProcess.rst +++ b/docs/configuration-directives/WSGIDaemonProcess.rst @@ -375,6 +375,12 @@ Options which can be supplied to the ``WSGIDaemonProcess`` directive are: to handle more requests, restarting of the process will be delayed if possible. + Note that when a process is restarted due to a request timeout, if the + Apache `LogLevel` is set to `info` or higher, or `wsgi:info` applied for + `LogLevel`, messages will be logged to the Apache error log file for the + request which gives the Python stack trace for any request handler threads + so you can work out where the request is blocking. + .. _deadlock-timeout: **deadlock-timeout=sss**