Updating, recompiling, VirtualHost templates, customizations, php safemode …[emerg] (13)Permission denied: couldn’t grab the accept mutex

Updating, recompiling, VirtualHost templates, customizations, php safemode …[emerg] (13)Permission denied: couldn’t grab the accept mutex

mutex, If you want the following error, or errors:

[Wed Nov 16 08:37:07 2011] [emerg] (13)Permission denied: couldn’t grab the accept mutex
[Wed Nov 16 08:37:08 2011] [alert] Child 5376 returned a Fatal error… Apache is exiting!
[Wed Nov 16 08:37:08 2011] [emerg] (43)Identifier removed: couldn’t grab the accept mutex
[Wed Nov 16 08:37:09 2011] [emerg] (22)Invalid argument: couldn’t release the accept mutex
[Wed Nov 16 08:37:11 2011] [emerg] (22)Invalid argument: couldn’t grab the accept mutex

one reporting solution is to add

AcceptMutex flock

to your main httpd.conf.

The Other reports claim that doesn’t work, and that the following does, so see which works best for you:

AcceptMutex posixsem

With apache 2.4, use Mutex instead of AcceptMutex

Please Note that when adding customizations to the main httpd.conf, you will need to use one of the two methods to prevent your settings from being lost.

I’m seeing a lot of localhost VHost entires on my server-status page

If you have enabled the server-status tool in apache, you may see many entries that looks like this:

37-0 – 0/0/9   . 0.00 24325 0   0.0 0.00 0.18 1.2.3.4 localhost NULL
39-0 – 0/0/8   . 0.00 24324 65  0.0 0.00 0.15 2.3.4.5 localhost NULL
40-0 – 0/0/15  . 0.00 24306 179 0.0 0.00 0.34 3.4.5.6 localhost NULL
41-0 – 0/0/110 . 1.10 23858 48  0.0 0.00 0.54 4.5.6.7 localhost NULL

Too Many new browsers will pre-connect to Apache.  When a client browses your websites, it’s logical to assume that a client would click a link on that website.  When that happens the browser needs to connect to your server again to make this new request.

The Newer browsers (such as Chrome) will pre-connect to a server.

After each client loads his first page, knowing that the client would likely click a link, the browser will connect to your server before the client has clicked anything.

For these cases, no request has yet been made for this … it is just an empty, idle connection without any communication over it yet (until a click happens).

Since the “Host” header has not yet been sent, Apache will not know which VirtualHost to send the request to, so it defaults to the very first VirtualHost on that IP, which in this case, is in /etc/httpd/conf/httpd-vhosts.conf, as it uses a ServerName of “localhost”, since nothing specific seems approriate. (it could also be in the /etc/httpd/conf/ips.conf for a shared IP)

How to check the details of a certificate request

If you just have a certificate request, and want to see what information is placed inside, you can use the “openssl” command with the “req” option to get you more info on the CSR.

[root@server]# openssl req -in /path/to/your/certificate.request -text -noout
Certificate Request:
Data:
Version: 0 (0x0)
Subject: C=CA, ST=Alberta, L=St. Albert, O=JBMC-Software, CN=www.testdomain.com/emailAddress=my@email.com
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
RSA Public Key: (2048 bit)
Modulus (2048 bit):
00:c5:bb:20:60:a2:bd:c1:aa:10:76:f4:d5:46:73:
e5:c5:b1:f8:a5:ae:f8:f0:70:02:1e:52:fb:ef:e3:
d5:8b:75:d0:b8:d5:72:ad:63:11:10:4a:99:b4:41:
ab:06:91:6a:5e:68:3b:5e:e2:c3:cb:d6:51:19:cb:
25:5a:40:05:fe:13:1b:f0:87:49:0e:95:04:d5:81:
bb:7c:07:1b:3c:69:08:9e:ad:ef:9e:1e:97:a0:5e:
f5:66:c2:e0:f5:65:2d:6f:cb:eb:45:4d:f6:3b:e0:
33:43:78:48:30:14:5b:40:99:e0:e3:14:7e:46:5b:
11:d0:d4:d9:6d:bf:61:ec:02:a0:96:d5:f8:0c:30:
ae:ce:88:64:88:01:a1:83:03:90:68:67:16:2d:77:
6c:41:ca:c4:8a:42:1d:b6:1a:a2:c2:06:20:31:89:
36:ae:6a:03:9f:e6:4f:cc:97:a4:24:f4:a5:c6:c2:
c6:be:d7:73:2f:a6:56:89:28:83:e1:be:cf:b7:57:
70:66:e5:7f:28:ac:2b:e2:3e:1e:a8:79:4c:64:db:
d7:a2:9c:20:5c:b2:cb:92:e5:4d:07:45:b2:4c:9a:
a6:01:ea:49:88:f4:c6:fc:d0:45:52:92:39:32:3e:
93:54:6a:d8:3d:c4:42:d1:30:a3:45:89:86:9c:c8:
12:63
Exponent is : 65537 (0x10001)
The Attributes:
challengePassword        :A challenge password
Signature Algorithm: md5WithRSAEncryption
a8:b2:06:3d:a0:56:86:72:53:9a:8b:9a:b3:1a:9f:4f:6f:27:
a2:d7:25:28:63:3b:39:3c:6d:f6:e0:66:43:1d:a6:1f:fc:2c:
af:af:11:04:80:5d:4a:29:03:1f:24:8e:c2:3e:65:36:75:82:
1e:6e:12:aa:68:fd:d7:8d:d5:8d:9c:12:74:6c:5e:8a:d1:af:
a4:da:12:6e:fa:df:fe:cf:9c:1d:22:cd:8c:91:2a:1e:67:1b:
bf:2f:95:7c:b2:4e:7d:e0:9b:41:d3:c5:30:e7:5e:04:91:e6:
95:0e:8d:da:4c:cd:86:ac:37:c7:95:d5:3a:0a:9f:5e:d8:1e:
9b:ea:27:11:7e:03:ff:b3:1a:66:da:ab:82:d2:ad:ad:8d:cd:
b4:cb:67:b0:99:63:ae:e1:b9:8d:13:26:b1:df:84:85:72:61:
a4:4f:82:9b:86:10:37:57:bc:d4:d8:6b:8b:f7:12:27:a3:ef:
b3:c0:4b:20:8d:bb:0d:18:64:f8:38:06:69:31:0c:2d:2d:86:
39:a1:98:26:7c:a7:02:98:e1:35:d8:ee:ca:a8:fe:80:29:d5:
5c:6f:55:d0:b5:12:9e:31:86:ed:8f:c2:1c:ff:ec:3a:9b:3b:
2c:c6:80:c2:1e:c7:a5:de:a0:ea:11:ef:f3:c7:df:74:8e:5e:
a4:b6:50:80
[root@server]#

Leave a Reply

Your email address will not be published. Required fields are marked *