That one PID 11454
has "2" connections, 16555 has "1",
values are 0, I guess it should become killed? - but it
it stays like this for a while (I don't know on what this
"while" depends on).
At this point all 3 rows are filled with stuff, such as:
But as you see, due to several _ this means that there are
not all 192 busy, in fact:
105 requests/sec - 2.5 MB/second - 24.8 kB/request
44 requests currently being processed, 20 idle workers
WHY can no others be used? With the statement above it means that
128 (which is 192-64) workers are unused because they should become
killed already, to spawn new ones, these are the ones in the 2. and
3. row with "G"s.
So the rest is occupied with "G". In Apache 2.2 I used MPM_event
as well, this obviously never occured because the both PIDs above
which are showing G only showed just dots in that case, now after
one PID should be finished, all slots become occupied with G,
which obviously causes a full scoreboard.
I would consider this a bug, a serious one for my case, since it
often occurs (~1-3 times per hour) that the server stops accepting
new requests, just because of that full scoreboard, where the server
is neither busy, nor do I see what configuration directive should
be configured badly. Again:
I assumed AsyncRequestWorkerFactor to have something to do
with it, I raised it from 2 (default) to 10, no change.
By the way: after some time (in this case above both) PIDs
become killed finally, releasing 2x64 slots in the scoreboard,
the waring messages vanish and the server can respond again
well to requests. In the interest of finding a workaround until
this is fixed: what configuration directives control that timeout
or whatever, which cause these PIDs to become killed?
On Thu, Sep 6, 2012 at 7:06 PM, Sam <email@example.com>
Yes, I still see such messages even after
upgrading to 2.4.3
On Sun, Aug 19, 2012 at 8:25 AM, Sam <firstname.lastname@example.org> wrote:
I upgraded to Apache 2.4 and use mod_event on a server
having average high load.
My issue is that I am getting pretty much often the error message
within the error log
AH00485: scoreboard is full, not at MaxRequestWorkers
What causes this? The server almost stops to handle new requests
when this occurs.
So you never have more than 192 simultaneous
requests at any given time ???