Apache Hung: Invalid argument:couldn ' t grab the Accept Mutex

Title, after starting a period of time, the number of processes decreased, the last left 10 or so, and error:

[emerg] (22)Invalid argument: couldn't grab the accept mutex

It didn't seem to have changed anything before, there was no problem. Is it the result of the most recent traffic (the number of httpd processes is up to 800 or so)?

StackOverflow have similar problems, another Baidu found some articles, there are two main methods:

1. MaxRequestsPerChildparameter setting problem;

2. Add a rowAcceptMutex posixsem

Have not tried, first to ask questions, and so try to see if you can solve.
See if anyone has ever met this problem.

Reference:

1. SF search Results

2. Apache maxrequestsperchild Command set unreasonable causes Apache to collapse bulb

3. Help! Apache keeps hanging.

4. Invalid argument:couldn ' t grab the accept mutex with Apache

This problem has arisen again today ... 50 days after the second time ...

[Wed Dec 09 10:12:33 2015] [Emerg] (22)  Invalid argument:couldn ' t grab the Accept mutex[wed Dec 10:12:35] [Emerg] ($) Invalid argument:couldn ' t grab the Accept mutex[wed Dec 10:12:35] [Emerg] (a) Invalid argument:couldn ' t grab the Accept mutex[wed Dec 09 10:12:35 2 015] [Emerg] (Invalid argument:couldn ' t grab the Accept mutex[wed Dec 10:12:35] [Emerg] (+) Invalid argument: Couldn ' t grab the Accept mutex[wed Dec 10:12:36] [Emerg] ($) Invalid argument:couldn ' t grab the Accept mutex[wed Dec 10:12:37] [Emerg] ($) Invalid argument:couldn ' t grab the Accept mutex[wed Dec 10:12:39] [Emerg] (+) I Nvalid argument:couldn ' t grab the Accept mutex[wed Dec 10:12:41] [Emerg] ($) Invalid argument:couldn ' t grab the Accept mutex[wed Dec 10:12:56] [Emerg] (a) Invalid argument:couldn ' t grab the Accept mutex[wed Dec 09 10:13:04 20 [Emerg] (Invalid argument:couldn ' t grab the Accept mutex[wed Dec 10:14:58] [Emerg] (INVA)Lid argument:couldn ' t grab the Accept Mutex 

Reply content:

Title, after starting a period of time, the number of processes decreased, the last left 10 or so, and error:

[emerg] (22)Invalid argument: couldn't grab the accept mutex

It didn't seem to have changed anything before, there was no problem. Is it the result of the most recent traffic (the number of httpd processes is up to 800 or so)?

StackOverflow have similar problems, another Baidu found some articles, there are two main methods:

1. MaxRequestsPerChildparameter setting problem;

2. Add a rowAcceptMutex posixsem

Have not tried, first to ask questions, and so try to see if you can solve.
See if anyone has ever met this problem.

Reference:

1. SF search Results

2. Apache maxrequestsperchild Command set unreasonable causes Apache to collapse bulb

3. Help! Apache keeps hanging.

4. Invalid argument:couldn ' t grab the accept mutex with Apache

This problem has arisen again today ... 50 days after the second time ...

[Wed Dec 09 10:12:33 2015] [Emerg] (22)  Invalid argument:couldn ' t grab the Accept mutex[wed Dec 10:12:35] [Emerg] ($) Invalid argument:couldn ' t grab the Accept mutex[wed Dec 10:12:35] [Emerg] (a) Invalid argument:couldn ' t grab the Accept mutex[wed Dec 09 10:12:35 2 015] [Emerg] (Invalid argument:couldn ' t grab the Accept mutex[wed Dec 10:12:35] [Emerg] (+) Invalid argument: Couldn ' t grab the Accept mutex[wed Dec 10:12:36] [Emerg] ($) Invalid argument:couldn ' t grab the Accept mutex[wed Dec 10:12:37] [Emerg] ($) Invalid argument:couldn ' t grab the Accept mutex[wed Dec 10:12:39] [Emerg] (+) I Nvalid argument:couldn ' t grab the Accept mutex[wed Dec 10:12:41] [Emerg] ($) Invalid argument:couldn ' t grab the Accept mutex[wed Dec 10:12:56] [Emerg] (a) Invalid argument:couldn ' t grab the Accept mutex[wed Dec 09 10:13:04 20 [Emerg] (Invalid argument:couldn ' t grab the Accept mutex[wed Dec 10:14:58] [Emerg] (INVA)Lid argument:couldn ' t grab the Accept Mutex 

