Two points here to clarify.
In your case the final error is:
Daemon process deadlock timer expired
This means that the full Python interpreter locked up. In this case the request
timeout may not apply and the feature where by stack traces can be dumped might
not happen. Depends on what lead
Adding to my recent post:
It seems that the `request-timeout=30` is effective, after all: The error
messages have changed, but there is no stack trace.
For completeness, here is the site config and error log excerpt:
Site config:
ServerAdmin webmaster@localhost
DocumentRoot
