Stefan,
if you consider configuration changes, you could also set the H2 worker threads
to a constant number. They have a minimum and maximum where mod_http2 creates
new worker when needed and releases some when idle. If you have not specified
anything via H2MinWorker/H2MaxWorker, then it
Hi,
Am 16.03.2017 um 18:05 schrieb Luca Toscano:
>
>
> 2017-03-16 15:24 GMT+01:00 Stefan Priebe - Profihost AG
> >:
>
> Hi,
>
> Am 16.03.2017 um 12:26 schrieb Luca Toscano:
> > Hi Stefan,
> >
> > 2017-03-16 12:14
2017-03-16 15:24 GMT+01:00 Stefan Priebe - Profihost AG <
s.pri...@profihost.ag>:
> Hi,
>
> Am 16.03.2017 um 12:26 schrieb Luca Toscano:
> > Hi Stefan,
> >
> > 2017-03-16 12:14 GMT+01:00 Stefan Priebe - Profihost AG
> > >:
> >
> > Hi Yann,
Hi,
Am 16.03.2017 um 12:26 schrieb Luca Toscano:
> Hi Stefan,
>
> 2017-03-16 12:14 GMT+01:00 Stefan Priebe - Profihost AG
> >:
>
> Hi Yann,
>
> no sure whether this is due to your mpm event patch.
>
> From time to time i see the
Hi Stefan,
2017-03-16 12:14 GMT+01:00 Stefan Priebe - Profihost AG <
s.pri...@profihost.ag>:
> Hi Yann,
>
> no sure whether this is due to your mpm event patch.
>
> From time to time i see the following error mesages in my logs and the
> only chance to fix it is to restart apache.
>
> [Thu Mar
Hello,
imho maxsparethreads is too low as well as maxrequestsperchild, which will
make your server reclaim threads too often, this often causes the
scoreboard full warning (although it is not an error, just a little
degradation from my experience testing).
Can you try to adjust maxsparethreads
Hi Yann,
no sure whether this is due to your mpm event patch.
>From time to time i see the following error mesages in my logs and the
only chance to fix it is to restart apache.
[Thu Mar 16 01:00:35.445184 2017] [mpm_event:error] [pid 27485:tid
140212799559552] AH: scoreboard is full, not at