> On 7 Feb 2018, at 3:14 pm, Jesus Cea <[email protected]> wrote: > > 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?.
Will work out what is best when get around to updating docs. I cleared out 60+ issues from issue tracker when I was on holiday a few weeks back. Next holiday not until April. :-) > 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. I'll look into. Python stack traces are a bit of a pain as they don't give a separate stack frame for when you call a function which is actually implemented in C code. Usually though one can at least work out the line in calling code where C function was called though. At least that is the case if using profile hooks. Don't remember what happens with stack frame dumping. Graham -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
