On Wed, Feb 1, 2017 at 1:02 PM, Niklas Edmundsson <[email protected]> wrote: > This might be due to processes being cleaned up due to hitting > MaxSpareThreads or MaxConnectionsPerChild, these are tuned to not happen > frequently. It's just a wild guess, but the reason for me suspecting this is > the weird looking stacktraces that points towards use-after-free issues...
The backtraces of the other threads in the process might give a hint if graceful proc shutdown is occurring -- e.g. one thread might have join_workers / apr_thread_join in the stack. -- Eric Covener [email protected]
