Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
To: users@httpd.apache.org
References: <20160509141658.026e4540@imp>
 <f88473f8-6146-30fe-c6e3-8e1670f6a9d8@christopherschultz.net>
 <20160509174557.0061e4df@imp>
From: Frank Gingras <francois.gingras@gmail.com>
Message-ID: <ee2bc344-00b0-9a50-7b0b-1cfe5fb74da5@gmail.com>
Date: Sat, 14 May 2016 22:17:05 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <20160509174557.0061e4df@imp>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [users@httpd] One page hanging entire server
archived-at: Sun, 15 May 2016 02:17:16 -0000


On 09/05/16 05:45 PM, D'Arcy J.M. Cain wrote:
> On Mon, 09 May 2016 16:26:19 -0400
> C> What kind of response were you getting from your server when you
>> connected with another client? Timeout? 503? 500?
>
> That's the point, they time out even if it is not a Wordpress or even a
> PHP page.  Simple HTML pages are getting blocked too.
>
>> If you tried to hit another WordPress page, it probably ALSO called
>> wp-cron.php which tried to hit the db to check for outstanding tasks,
>> and that call probably got blocked by a db record or table lock.
>>
>> I'm guessing this is really a question for the WordPress community.
>
> Maybe if it only blocked WP sites but it blocks all of them.
>


What mpm are you using? How many idle workers did you have then?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org