Chris McDonough wrote:
Hmmm... it might be useful to turn on detailed request logging (-M logging) in the start file (see z2.py).
OK, this is done now...
Attached is a script that I just checked into the trunk to do analysis of the file generated by the -M log. It can help you figure out if there's a pattern to the hangs (whether it happens on a particular method, whether it happens at heavy load time, whether it happens at a particular time of day, etc.) Do you think you'd be willing to play around with it a little bit to try to discover a pattern?
Definitely, can you help me with 'reading the runes'? cheers, Chris PS:
4. restart usually yields a .trX file (an aborted transaction I suppose)
I didn't get any .tr? files, and no, I didn't rm them either ;-)