On Fri, Sep 7, 2012 at 12:57 AM, Igor Cicimov icici...@gmail.com wrote:
On Thu, Sep 6, 2012 at 11:21 PM, Sam lenn...@chello.at 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:
PID
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,
Yes, I still see such messages even after upgrading to 2.4.3
On Sun, Aug 19, 2012 at 8:25 AM, Samlenn...@chello.at 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
baby baby
On Thu, Sep 6, 2012 at 10:06 AM, Sam lenn...@chello.at wrote:
**
Yes, I still see such messages even after upgrading to 2.4.3
On Sun, Aug 19, 2012 at 8:25 AM, Sam lenn...@chello.at lenn...@chello.at
wrote:
I upgraded to Apache 2.4 and use mod_event on a server
having
On Thu, Sep 6, 2012 at 7:06 PM, Sam lenn...@chello.at wrote:
**
Yes, I still see such messages even after upgrading to 2.4.3
On Sun, Aug 19, 2012 at 8:25 AM, Sam lenn...@chello.at lenn...@chello.at
wrote:
I upgraded to Apache 2.4 and use mod_event on a server
having average high load.
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
On Thu, Sep 6, 2012 at 11:21 PM, Sam lenn...@chello.at 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
totalacceptingbusy
On Sun, Aug 19, 2012 at 8:25 AM, Sam lenn...@chello.at 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
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 lenn...@chello.at 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
