Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E0038DD29 for ; Thu, 6 Sep 2012 09:13:04 +0000 (UTC) Received: (qmail 1953 invoked by uid 500); 6 Sep 2012 09:13:02 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 1241 invoked by uid 500); 6 Sep 2012 09:12:55 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 1206 invoked by uid 99); 6 Sep 2012 09:12:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Sep 2012 09:12:53 +0000 X-ASF-Spam-Status: No, hits=2.9 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [62.179.121.40] (HELO fep20.mx.upcmail.net) (62.179.121.40) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Sep 2012 09:12:46 +0000 Received: from edge03.upcmail.net ([192.168.13.238]) by viefep20-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20120906091224.UBVS26345.viefep20-int.chello.at@edge03.upcmail.net> for ; Thu, 6 Sep 2012 11:12:24 +0200 Received: from [84.112.232.120] ([84.112.232.120]) by edge03.upcmail.net with edge id vlCP1j00t2cXBx803lCQ4S; Thu, 06 Sep 2012 11:12:24 +0200 X-SourceIP: 84.112.232.120 X-Authenticated-Sender: lennsen Message-ID: <5048678B.2030907@chello.at> Date: Thu, 06 Sep 2012 11:06:19 +0200 From: Sam User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.24) Gecko/20111108 Mandriva/3.1.16-0.1mdv2010.2 (2010.2) Thunderbird/3.1.16 MIME-Version: 1.0 To: users@httpd.apache.org References: <5030CD1C.5020406@chello.at> In-Reply-To: Content-Type: multipart/alternative; boundary="------------040100000801080008040408" Subject: Re: [users@httpd] scoreboard is full, not at MaxRequestWorkers --------------040100000801080008040408 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: scoreboard is full, not at MaxRequestWorkers >>> >>> What causes this? The server almost stops to handle new requests >>> when this occurs. >>> >>> MaxRequestWorkers 192 >>> ServerLimit 3 >>> StartServers 2 >>> >>> MaxMemFree 2048 >>> MinSpareThreads 64 >>> MaxSpareThreads 64 >>> ThreadLimit 64 >>> ThreadsPerChild 64 >>> MaxConnectionsPerChild 10240 >>> AsyncRequestWorkerFactor 2 > Just in case you still have this issue, we've switched to 2.4.3 after > seeing a few bug reports that could be related, and since then I > haven't seen this again. > > Regards, > > Martin --------------040100000801080008040408 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Yes, I still see such messages even after upgrading to 2.4.3

On Sun, Aug 19, 2012 at 8:25 AM, Sam <lennsen@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 causes this? The server almost stops to handle new requests
when this occurs.

MaxRequestWorkers 192
ServerLimit         3
StartServers        2

MaxMemFree                2048
MinSpareThreads             64
MaxSpareThreads             64
ThreadLimit                 64
ThreadsPerChild             64
MaxConnectionsPerChild   10240
AsyncRequestWorkerFactor     2

Just in case you still have this issue, we've switched to 2.4.3 after
seeing a few bug reports that could be related, and since then I
haven't seen this again.

Regards,

Martin

--------------040100000801080008040408--