Hello Graham, thanks for your tip. I set the request-timeout to 30 seconds (well shorter than Apache's patience), and lo and behold, the timeout errors have stopped appearing in the logs altogether.
Now I'm wondering: Since the request-timeout parameter makes mod_wsgi restart itself before Apache kills it from outside, is it possible that my code gets stuck as before but the timeout isn't logged at all? I was hoping that hitting mod_wsgi's request-timeout limit would trigger a meaningful stack trace into the Apache logs. Or possibly my script just happened to not hang since a couple of days ago (it did it about once per day before). Best regards: **D On Monday, June 8, 2020 at 12:46:36 PM UTC+2, Graham Dumpleton wrote: > > You need to set the request-timeout option on WSGIDaemonProcess. > > On 8 Jun 2020, at 6:01 pm, Daniel Haude <danie...@gmail.com <javascript:>> > 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 mod...@googlegroups.com <javascript:>. > 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 modwsgi+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/modwsgi/de0b5052-647f-43d7-89f5-07af5cfa1f94o%40googlegroups.com.
