Skip to main content

Apache Crash: Permission denied: AH00144: couldn't grab the accept mutex

Comments

11 comments

  • cPanelMichael
    Hello :) I found a couple of cases where enabling piped logging via "WHM Home " Service Configuration " Apache Configuration " Piped Log Configuration" resolved this issue. Could you try enabling piped logging, and removing any custom changes you made to initially resolve the issue? Thank you.
    0
  • monkey64
    No luck cPanelMichael. It crashed a couple of hours after I removed the custom changes and enabled piped logging. Here is another output: [Mon Nov 04 17:33:27.827354 2013] [core:alert] [pid 8313] AH00050: Child 28075 returned a Fatal error... Apache is exiting! [Mon Nov 04 17:33:27.839808 2013] [mpm_prefork:emerg] [pid 26086] (43)Identifier removed: AH00144: couldn't grab the accept mutex [Mon Nov 04 17:33:27.843412 2013] [mpm_prefork:emerg] [pid 29130] (43)Identifier removed: AH00144: couldn't grab the accept mutex [Mon Nov 04 17:33:27.846220 2013] [mpm_prefork:emerg] [pid 28074] (43)Identifier removed: AH00144: couldn't grab the accept mutex [Mon Nov 04 17:33:27.849052 2013] [mpm_prefork:emerg] [pid 29162] (43)Identifier removed: AH00144: couldn't grab the accept mutex [Mon Nov 04 17:33:27.849406 2013] [mpm_prefork:emerg] [pid 29160] (43)Identifier removed: AH00144: couldn't grab the accept mutex [Mon Nov 04 17:33:27.851990 2013] [mpm_prefork:emerg] [pid 29041] (43)Identifier removed: AH00144: couldn't grab the accept mutex [Mon Nov 04 17:33:27.852454 2013] [mpm_prefork:emerg] [pid 29161] (43)Identifier removed: AH00144: couldn't grab the accept mutex [Mon Nov 04 17:33:33.661534 2013] [mpm_prefork:emerg] [pid 27882] (22)Invalid argument: AH00144: couldn't grab the accept mutex [Mon Nov 04 17:33:47.644485 2013] [mpm_prefork:emerg] [pid 27419] (22)Invalid argument: AH00146: couldn't release the accept mutex [Mon Nov 04 17:35:56.097004 2013] [suexec:notice] [pid 30073] AH01232: suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
    0
  • cPanelMichael
    In response to your other question in your initial post, yes, the following value is sometimes recommended: AcceptMutex posixsem
    If you want to avoid directly editing and distilling the Apache configuration file, you can add this line directly to the following file: /usr/local/apache/conf/mod_ruid2.conf
    You will find this in our documentation: Apache Mod_Ruid2 Does the issue continue when adding this value? Thank you.
    0
  • monkey64
    The issue seems to be resoved, many thanks Michael.
    0
  • monkey64
    Actaully, I spoke too soon. The problem is not fixed and Apache crashed again... I checked that my change had been distilled, and sure enough found the line: Mutex posixsem
    in httpd.conf. DSO seems to be unstable so I have temporarily switched back to Suexec. There is obviously an issue when I run DSO. What do I do now?
    0
  • cPanelMichael
    You are welcome to open a support ticket if you want us to take a closer look: Submit A Ticket Post the ticket number here and we can update this thread with the outcome. Thank you.
    0
  • monkey64
    I followed the instruction on the Cpanel Apache Mod_Ruid2 page: "To resolve this issue, you may add the following line to /usr/local/apache/conf/mod_ruid2.conf:" AcceptMutex posixsem So here is my mod_ruid2.conf file: RMode config RDefaultUidGid nobody nobody RUidGid nobody nobody AcceptMutex posixsem
    And here is the output once I restarted Apache: Apache restart failed. Unable to load pid from pid file and no httpd process found in process list. If apache restart reported success but it failed soon after, it may be caused by oddities with mod_ssl. You should run /usr/local/cpanel/scripts/ssl_crt_status as part of your troubleshooting process. Pass it --help for more details. Also be sure to examine apache's various log files. Apache Restart Output: Log: [Mon Dec 09 08:56:34.004436 2013] [:notice] [pid 32286] ModSecurity: PCRE compiled version="8.21 "; loaded version="8.21 2011-12-12" [Mon Dec 09 08:56:34.004446 2013] [:notice] [pid 32286] ModSecurity: LUA compiled version="Lua 5.1" [Mon Dec 09 08:56:34.004455 2013] [:notice] [pid 32286] ModSecurity: LIBXML compiled version="2.9.0" [Mon Dec 09 08:56:35.008221 2013] [:notice] [pid 32287] mod_ruid2/0.9.8 enabled [Mon Dec 09 08:56:35.034803 2013] [mpm_prefork:notice] [pid 32287] AH00163: Apache/2.4.7 (Unix) OpenSSL/0.9.8e-fips-rhel5 mod_bwlimited/1.4 PHP/5.4.22 configured -- resuming normal operations [Mon Dec 09 08:56:35.034889 2013] [core:notice] [pid 32287] AH00094: Command line: '/usr/local/apache/bin/httpd -D SSL' [Mon Dec 09 08:57:31.255902 2013] [mpm_prefork:notice] [pid 32287] AH00171: Graceful restart requested, doing restart [Mon Dec 09 08:57:32.006902 2013] [:notice] [pid 32287] mod_ruid2/0.9.8 enabled [Mon Dec 09 08:57:32.038743 2013] [mpm_prefork:notice] [pid 32287] AH00163: Apache/2.4.7 (Unix) OpenSSL/0.9.8e-fips-rhel5 mod_bwlimited/1.4 PHP/5.4.22 configured -- resuming normal operations [Mon Dec 09 08:57:32.038772 2013] [core:notice] [pid 32287] AH00094: Command line: '/usr/local/apache/bin/httpd -D SSL' [Mon Dec 09 08:58:44.174091 2013] [mpm_prefork:notice] [pid 32287] AH00169: caught SIGTERM, shutting down
    I should point out that removing "AcceptMutex posixsem" allows Apache to restart correctly. There seems to be a mod_ssl error. I checked the Service Certificates in Home " Service Configuration " Manage Service SSL Certificates and they are all valid and expire next year. Any ideas?
    0
  • cPanelMichael
    Could you open a support ticket using the link in my signature so we can take a closer look? You can post the ticket number here so we can update this thread with the outcome. Thank you.
    0
  • monkey64
    [quote="cPanelMichael, post: 1496972">In response to your other question in your initial post, yes, the following value is sometimes recommended: AcceptMutex posixsem

    That didn't work for me. I found that adding: Mutex posixsem
    to mod_ruid2.conf at last solved the problem. I tried adding the line to http.conf and distilling, but the only way I got it to work was to edit mod_ruid2.conf directly. BTW: I'm running Apache 2.4.7.
    0
  • KurtN.
    I wasn't able to duplicate your issue with respect to changing mutex's using the new Mutex directive in Apache 2.4. Here are the steps I used to do so successfully: [list]
  • Look for the following lines in httpd.conf Mutex default mpm-accept
  • Change it to Mutex posixsem mpm-accept
  • Run the distiller # /usr/local/cpanel/bin/apache_conf_distiller --update --store-data Distilled successfully
  • Ensure it distilled correctly # /usr/local/cpanel/bin/build_apache_conf Built /usr/local/apache/conf/httpd.conf OK
  • 0
  • paoloie
    I have been getting a lot of server failures lately too. The error log shows that "couldn't grab the accept mutex" line every time if crashes. The server Automagically restarts every time but I want to get rid of the error. So I tried adding AcceptMutex posixsem
    to /usr/local/apache/conf/mod_ruid2.conf
    But the server would not restart after that, so I had to take that line back out. Then it restarted. I have now enables Piped Apache Logs and will wait to see if it falls over again. In the meantime, is there something else I could try if it does? Thanks Paoloie
    0

Please sign in to leave a comment.