It's probably worth looking at the debug pages to see what queries are active. Probably also worth grabbing stack traces with gdb or core dumps with gcore. If it's a hang then it's often possible to diagnose from the backtraces.
Could also be worth running perf top to see where it's spending time (if anywhere). On Wed, Nov 16, 2016 at 5:19 PM, Jim Apple <[email protected]> wrote: > I'm running the EE tests on a machine and it seems to be stuck in the > stress tests. I have access to the machine for now, but my Jenkins > install is going to steal it from me when the job is force-timed-out > in a few hours. What should I look at now to try and understand what > is happening - in particular, what could be useful to me now but not > visible in the logs? >
