Re: [users@httpd] scoreboard is full, not at MaxRequestWorkers

2012-09-07 Thread Sam
Changing KeepAlive to Off does not help, the issue occurs at this point where obviously due to MaxConnectionsPerChild a Process should become killed. As observed, the problem is that (in the example stated) both PIDs 11454 and 16555 do not become killed because of these remaining connections, whi

Re: [users@httpd] scoreboard is full, not at MaxRequestWorkers

2012-09-07 Thread Tom Evans
On Fri, Sep 7, 2012 at 12:57 AM, Igor Cicimov wrote: > On Thu, Sep 6, 2012 at 11:21 PM, Sam wrote: >> >> Never, the server is not even under high load. There >> are several thousand vhosts, it is about shared webhosting. >> >> This is what server-status says: >> >> PIDConnections Threads

Re: [users@httpd] scoreboard is full, not at MaxRequestWorkers

2012-09-06 Thread Igor Cicimov
On Thu, Sep 6, 2012 at 11:21 PM, Sam wrote: > ** > Never, the server is not even under high load. There > are several thousand vhosts, it is about shared webhosting. > > This is what server-status says: > > PIDConnections ThreadsAsync connections > totalacceptingbusyidle

Re: [users@httpd] scoreboard is full, not at MaxRequestWorkers

2012-09-06 Thread Sam
Never, the server is not even under high load. There are several thousand vhosts, it is about shared webhosting. This is what server-status says: PIDConnections ThreadsAsync connections totalacceptingbusyidlewritingkeep-aliveclosing 21388257yes 44 2

Re: [users@httpd] scoreboard is full, not at MaxRequestWorkers

2012-09-06 Thread Igor Cicimov
On Thu, Sep 6, 2012 at 7:06 PM, Sam wrote: > ** > > Yes, I still see such messages even after upgrading to 2.4.3 > > On Sun, Aug 19, 2012 at 8:25 AM, Sam > 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 m

Re: [users@httpd] scoreboard is full, not at MaxRequestWorkers

2012-09-06 Thread Andre Catao
baby baby On Thu, Sep 6, 2012 at 10:06 AM, Sam wrote: > ** > > Yes, I still see such messages even after upgrading to 2.4.3 > > > On Sun, Aug 19, 2012 at 8:25 AM, Sam > wrote: > > I upgraded to Apache 2.4 and use mod_event on a server > having average high load. > > My issue is that I am ge

Re: [users@httpd] scoreboard is full, not at MaxRequestWorkers

2012-09-06 Thread Sam
Yes, I still see such messages even after upgrading to 2.4.3 On Sun, Aug 19, 2012 at 8:25 AM, Sam 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: scoreboar

Re: [users@httpd] scoreboard is full, not at MaxRequestWorkers

2012-08-28 Thread Martin S
On Sun, Aug 19, 2012 at 8:25 AM, Sam 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

Re: [users@httpd] scoreboard is full, not at MaxRequestWorkers

2012-08-27 Thread Martin S
Hello Sam, We're having the same exact issue. Did you found the solution? Cheers, Martin On Sun, Aug 19, 2012 at 8:25 AM, Sam 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 > with

[users@httpd] scoreboard is full, not at MaxRequestWorkers

2012-08-19 Thread Sam
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 thi