On Wed, 1 Feb 2017, Eric Covener wrote:
On Wed, Feb 1, 2017 at 1:02 PM, Niklas Edmundsson 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
On Wed, Feb 1, 2017 at 8:32 PM, wrote:
>
> 2.4.x patch:
> http://home.apache.org/~ylavic/patches/httpd-2.4.x-r1740928_and_co-v2.patch
> +1: ylavic
> + rpluem says: Please add r1781299
Actually I've just reverted r1781188 (and your r1781299) to split the
two
As RĂ¼diger wrote, this stacktrace does not make any sense (to me), unless the
pool cleanup messes up the stack.
Hmmm. This points to a major misconception of mine how things are supposed to
happen. Will continue to look at this, but no easy solution in sight.
> Am 27.01.2017 um 20:30 schrieb
On Wed, Feb 1, 2017 at 1:02 PM, Niklas Edmundsson 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
>
Hi all!
We've started to see spurious segfaults with httpd 2.4.25, mpm_event,
ssl on Ubuntu 14.04LTS. Not frequent, but none the less happening.
This might be due to processes being cleaned up due to hitting
MaxSpareThreads or MaxConnectionsPerChild, these are tuned to not
happen