You need to set the request-timeout option on WSGIDaemonProcess. > On 8 Jun 2020, at 6:01 pm, Daniel Haude <[email protected]> wrote: > > Hello, > > about once a day I'm getting "Timeout when reading response headers from > daemon process" from my WSGI/Flask application, of course never when I > test/use the app myself. I'd like to find out at which point the code hangs. > The MySQL "long query" or error logs doesn't showe anything, but I'm also > attaching to other DBs where I don't have access to the logs. > > In the mod_wsgi logs I found this paragraph: "When stack traces were being > dumped upon request timeout expiring, the line numbers of the definition of > each function in the stack trace was being displayed, instead of the actual > line number within the body of the function that was executing at the time." > , so it must be possible to get stack traces, only there is no hint on how to > activate them. > > Thanks! > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/modwsgi/b4204300-ca26-4d26-8251-219a06846837o%40googlegroups.com > > <https://groups.google.com/d/msgid/modwsgi/b4204300-ca26-4d26-8251-219a06846837o%40googlegroups.com?utm_medium=email&utm_source=footer>.
-- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/modwsgi/E9380B93-1A58-4FE7-B5D4-4F02289DAD4E%40gmail.com.
