On 07/02/18 03:55, Graham Dumpleton wrote: > On this specific issue, it will logs lots of stuff if you have Apache log > level set to info. > > LogLevel info > > For request-timeout expiring it even logs stack traces for you if it can so > you can see where it gets stuck.
Not documented :-). Could you possibly change "LogLevel info" to "LogLevel wsgi:info" in the docs?. Also, traceback is partial when a thread is inside a C routine, because it is showed as the last called C function and the line number of the entry point. We can not see in what line is it waiting for a lock, for instance. For instance, I am causing a deadlock on purpose and I am seeing this: """ [Wed Feb 07 04:43:41.021026 2018] [wsgi:info] [pid 27347:tid 140119465424768] mod_wsgi (pid=27347): Thread 140119266129664 executing file "/home/buffy/wsgi.py", line 449, in get_listado """ Line 449 is the "def get_listado()" definition line, not the "with lock" line inside that function that is actually waiting for the lock. I see the same effect in all the traceback: the documented line numbers are the starting line of each calling function, not the linenumber of the actual call. Is this a bug?. -- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:j...@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -- 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 post to this group, send email to modwsgi@googlegroups.com. Visit this group at https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature