I am setting up a internal virtual host on Apache with a self signed certificate. I have my VirtualHost config and when I try to start Apache, I get an error stating the cert if either missing or empty. I have checked my persmissions and cert and everything looks proper so I'm not sure why i'm getting this error. What is wrong with my config?
VirtualHost config:
<VirtualHost *:443>
ServerName www1
ServerAlias www1
DocumentRoot /var/www/html
SSLEngine on
SSLCertificateFile /var/certs/www-cert.crt
SSLCertificateKeyFile /var/certs/www-cert.key
</VirtualHost>
The error from apache:
[root#www1 scripts]# systemctl status httpd
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2016-12-17 16:13:50 CST; 44s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 10109 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 10107 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 10107 (code=exited, status=1/FAILURE)
Dec 17 16:13:50 www1 systemd[1]: Starting The Apache HTTP Server...
Dec 17 16:13:50 www1 httpd[10107]: AH00526: Syntax error on line 6 of /etc/httpd/conf.d/default.conf:
Dec 17 16:13:50 www1 httpd[10107]: SSLCertificateFile: file '/var/certs/www-cert.crt' does not exist or is empty
Dec 17 16:13:50 www1 systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Dec 17 16:13:50 www1 kill[10109]: kill: cannot find process ""
Dec 17 16:13:50 www1 systemd[1]: httpd.service: control process exited, code=exited status=1
Dec 17 16:13:50 www1 systemd[1]: Failed to start The Apache HTTP Server.
Dec 17 16:13:50 www1 systemd[1]: Unit httpd.service entered failed state.
Dec 17 16:13:50 www1 systemd[1]: httpd.service failed.
The cert does exist:
[root#www1 scripts]# ls -la /var/certs
total 12
drwxr-xr-x. 2 root root 44 Dec 17 16:13 .
drwxr-xr-x. 22 root root 4096 Dec 17 14:57 ..
-rwxr-xr-x. 1 root root 1253 Dec 17 16:13 www-cert.crt
-rwxr-xr-x. 1 root root 1704 Dec 17 16:13 www-cert.key
The cert is valid:
[root#www1 scripts]# openssl x509 -text -noout -in /var/certs/www-cert.crt
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 17817470849210419499 (0xf7445f561b10892b)
Signature Algorithm: sha256WithRSAEncryption
Issuer: C=CA, ST=Manitoba, OU=www1/emailAddress=root#localhost
Validity
Not Before: Dec 17 22:13:49 2016 GMT
Not After : Dec 11 22:13:49 2021 GMT
Subject: C=CA, ST=Manitoba, OU=www1/emailAddress=root#localhost
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)
Modulus:
00:b2:76:fa:a8:8a:0d:ee:97:2f:5c:f8:7d:2a:48:
e9:f8:ce:c6:df:62:5f:23:e4:be:ea:c0:9c:25:09:
31:30:df:90:fc:6b:1b:58:62:98:29:aa:13:39:93:
bc:4d:d2:b8:7a:9f:e8:09:c1:e6:dc:1d:57:67:67:
33:61:6e:eb:a8:52:a6:77:70:19:ed:2a:58:5a:79:
35:ba:af:18:c2:2f:be:06:6a:8b:33:12:e7:63:03:
63:12:36:ed:ae:8e:c5:13:b5:2a:be:25:ac:dc:8a:
a5:dc:bc:86:49:27:29:7f:cd:5e:e1:ec:d9:a5:9f:
34:63:cc:7b:34:fa:2e:27:da:7b:90:a2:27:46:9b:
0b:e1:0a:68:a2:ed:df:1a:b6:48:ef:4f:c9:23:a8:
cf:7e:4c:da:ff:1f:80:52:fb:15:10:39:03:b5:d2:
0d:64:4b:df:9c:0f:41:9a:a0:d8:a1:c7:25:aa:19:
ee:c6:01:81:8b:be:7a:d8:c6:8c:cd:8f:13:51:68:
6d:78:00:72:76:d7:19:9b:d1:66:73:43:4b:30:9b:
de:96:29:81:80:40:31:39:43:e1:c4:2c:4a:c0:19:
4e:9b:d1:f5:e7:2b:d5:36:e3:eb:ef:31:e5:32:b1:
53:5b:f7:a5:c1:17:94:e9:ab:79:e2:02:be:c0:6f:
98:b1
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Subject Key Identifier:
2C:E5:06:10:BB:24:32:27:7A:7F:50:00:A8:A5:D6:FC:86:5C:58:1F
X509v3 Authority Key Identifier:
keyid:2C:E5:06:10:BB:24:32:27:7A:7F:50:00:A8:A5:D6:FC:86:5C:58:1F
X509v3 Basic Constraints:
CA:TRUE
Signature Algorithm: sha256WithRSAEncryption
05:69:cb:ee:4d:b5:3c:cb:c4:fb:2f:ac:26:b8:fd:db:bf:41:
69:d0:a2:5b:cd:cc:04:53:f5:32:fc:7d:c9:fb:54:9d:d4:bf:
41:02:09:0a:19:51:b1:69:bb:87:87:34:91:28:d4:1d:64:49:
3e:38:27:ad:74:91:4a:e2:dc:85:4f:56:92:ad:fe:f1:9d:17:
ca:e7:b2:2f:2f:89:62:fd:47:a0:0d:67:fb:6b:3b:8a:59:ae:
73:03:97:72:c7:4c:d7:23:a3:b7:1f:ed:8a:bf:03:8a:00:40:
1b:b4:02:d5:f6:73:45:4b:fd:1b:44:9d:9d:46:ca:c1:30:a0:
53:5d:a3:2b:da:09:84:e6:97:9c:66:e5:a2:92:12:99:c5:03:
7f:b7:f6:03:3d:d8:f3:ea:72:f4:ce:2b:73:dd:c6:72:e7:fb:
55:6e:b5:44:11:52:56:ce:3d:0b:d8:40:cb:7e:ed:89:06:c6:
ec:3a:0b:94:e7:54:ce:5e:d6:13:1f:3e:9f:35:47:9b:46:89:
97:80:62:14:f7:40:3e:f6:bc:d9:16:7e:c3:51:27:eb:ab:db:
80:d8:7e:ae:e5:a8:bb:09:28:73:ae:07:1f:78:79:b5:df:5f:
60:85:c3:1e:93:29:95:4e:92:c2:96:e8:ec:a8:46:51:05:a3:
eb:3d:96:f2
Related
[ec2-user#tower1 ~]$ systemctl status httpd.service -l
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2021-10-28 12:13:49 UTC; 5min ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 12139 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 12137 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 12137 (code=exited, status=1/FAILURE)
Oct 28 12:13:49 tower1.12c2.internal httpd[12137]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Oct 28 12:13:49 tower1.12c2.internal httpd[12137]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Oct 28 12:13:49 tower1.12c2.internal httpd[12137]: no listening sockets available, shutting down
Oct 28 12:13:49 tower1.12c2.internal httpd[12137]: AH00015: Unable to open logs
Oct 28 12:13:49 tower1.12c2.internal systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Oct 28 12:13:49 tower1.12c2.internal kill[12139]: kill: cannot find process ""
Oct 28 12:13:49 tower1.12c2.internal systemd[1]: httpd.service: control process exited, code=exited status=1
Oct 28 12:13:49 tower1.12c2.internal systemd[1]: Failed to start The Apache HTTP Server.
Oct 28 12:13:49 tower1.12c2.internal systemd[1]: Unit httpd.service entered failed state.
Oct 28 12:13:49 tower1.12c2.internal systemd[1]: httpd.service failed.
I'm running few things on CentOS 7. Everything was working fine until full update with yum update. Can't launch Apache since.
I tried everything including removing and reinstalling httpd.
The error I'm getting is this:
**systemctl status httpd.service**
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2020-07-09 20:50:18 CEST; 34min ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 5785 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 5785 (code=exited, status=1/FAILURE)
Jul 09 20:50:18 vps.xyz.com systemd[1]: Starting The Apache HTTP Server...
Jul 09 20:50:18 vps.xyz.com httpd[5785]: [Thu Jul 09 20:50:18.618214 2020] [so:warn] [pid 5785] AH01574: module systemd_module is already ...skipping
Jul 09 20:50:18 vps.xyz.com httpd[5785]: AH00526: Syntax error on line 1 of /etc/httpd/conf/httpd.conf:
Jul 09 20:50:18 vps.xyz.com httpd[5785]: Invalid command '\xef\xbb\xbfServerRoot', perhaps misspelled or defined by a module not included ...guration
Jul 09 20:50:18 vps.xyz.com systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Jul 09 20:50:18 vps.xyz.com systemd[1]: Failed to start The Apache HTTP Server.
Jul 09 20:50:18 vps.xyz.com systemd[1]: Unit httpd.service entered failed state.
Jul 09 20:50:18 vps.xyz.com systemd[1]: httpd.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
It doesn't matter how I edit httpd.conf, it always shows me the same \xef\xbb\xbf error.
Looks like an encoding issue. Could you please encoding type of httpd.conf file. It should be UTF-8 Unicode text
file httpd.conf
i.e
[test#test bin]# file /etc/httpd/conf/httpd.conf
/etc/httpd/conf/httpd.conf: UTF-8 Unicode text
On Notepad++ you can use the Encoding -> Encode in UTF-8 without BOM option to remove it
are they any Centos 7 / Apache 2.4.6 experts out there?
I am a newbie at web servers, but I have read Go Daddy's Support instructions, Apache HTTPD support sites, and every other Support Forum I can find about this issue.
I have setup the Centos 7 server with HTTPD 2.4.6. I created the Private Key with Open SSL and the CSR and sent the request to Go Daddy. I received back three files: the Server Certificate File and the CA Bundle File. I have copied these files to my server. I have setup the virtual host configuration files with:
<VirtualHost *:443>
ServerName www.laggersec.org
ServerAlias laggersec.org
DocumentRoot /var/www/laggersec.org/html
ErrorLog /var/www/laggersec.org/log/error.log
CustomLog /var/www/laggersec.org/log/requests.log combined
SSLEngine on
SSLProtocol -all +TLSv1.2
SSLCertificateFile /etc/ssl/certs/laggersec.org.crt
SSLCertificateKeyFile /etc/ssl/certs/private/laggersec.org.key
SSLCertificateChainFile /etc/ssl/certs/intermediate.crt
</VirtualHost>
However, whenever I start httpd, it fails with an error.
[root#LAGGERSEC1WEB1 slaggeradmin04]# apachectl restart
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
[root#LAGGERSEC1WEB1 slaggeradmin04]# systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2020-03-23 17:24:10 UTC; 10s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 116366 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 116365 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 116365 (code=exited, status=1/FAILURE)
Mar 23 17:24:10 LAGGERSEC1WEB1 systemd[1]: Starting The Apache HTTP Server...
Mar 23 17:24:10 LAGGERSEC1WEB1 systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Mar 23 17:24:10 LAGGERSEC1WEB1 kill[116366]: kill: cannot find process ""
Mar 23 17:24:10 LAGGERSEC1WEB1 systemd[1]: httpd.service: control process exited, code=exited status=1
Mar 23 17:24:10 LAGGERSEC1WEB1 systemd[1]: Failed to start The Apache HTTP Server.
Mar 23 17:24:10 LAGGERSEC1WEB1 systemd[1]: Unit httpd.service entered failed state.
Mar 23 17:24:10 LAGGERSEC1WEB1 systemd[1]: httpd.service failed.
[root#LAGGERSEC1WEB1 slaggeradmin04]# journalctl -xe
--
-- Unit user-0.slice has finished starting up.
--
-- The start-up result is done.
Mar 23 17:24:01 LAGGERSEC1WEB1 systemd[1]: Started Session 1533 of user root.
-- Subject: Unit session-1533.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-1533.scope has finished starting up.
--
-- The start-up result is done.
Mar 23 17:24:02 LAGGERSEC1WEB1 CROND[116341]: (root) CMD ([ -f /etc/krb5.keytab ] && [ \( ! -f /etc/opt/omi/creds/omi.keytab \) -o \( /etc/krb5.keytab
Mar 23 17:24:02 LAGGERSEC1WEB1 systemd[1]: Removed slice User Slice of root.
-- Subject: Unit user-0.slice has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-0.slice has finished shutting down.
Mar 23 17:24:10 LAGGERSEC1WEB1 polkitd[616]: Registered Authentication Agent for unix-process:116359:6177048 (system bus name :1.3444 [/usr/bin/pkttyag
Mar 23 17:24:10 LAGGERSEC1WEB1 systemd[1]: Starting The Apache HTTP Server...
-- Subject: Unit httpd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has begun starting up.
Mar 23 17:24:10 LAGGERSEC1WEB1 systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Mar 23 17:24:10 LAGGERSEC1WEB1 kill[116366]: kill: cannot find process ""
Mar 23 17:24:10 LAGGERSEC1WEB1 systemd[1]: httpd.service: control process exited, code=exited status=1
Mar 23 17:24:10 LAGGERSEC1WEB1 systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit httpd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has failed.
--
-- The result is failed.
Mar 23 17:24:10 LAGGERSEC1WEB1 systemd[1]: Unit httpd.service entered failed state.
Mar 23 17:24:10 LAGGERSEC1WEB1 systemd[1]: httpd.service failed.
Mar 23 17:24:10 LAGGERSEC1WEB1 polkitd[616]: Unregistered Authentication Agent for unix-process:116359:6177048 (system bus name :1.3444, object path /o
lines 4447-4486/4486 (END)
[root#LAGGERSEC1WEB1 slaggeradmin04]# cd /var/log/httpd
[root#LAGGERSEC1WEB1 httpd]# ls
access_log error_log-20200308 off ssl_error_log ssl_request_log-20200308
access_log-20200308 error_log-20200315 ssl_access_log ssl_error_log-20200308 system_u:object_r:etc_t:s0
error_log error_log-20200322 ssl_access_log-20200308 ssl_request_log
[root#LAGGERSEC1WEB1 httpd]# cat error_log
[Sun Mar 22 13:41:32.406464 2020] [suexec:notice] [pid 72981] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Mar 22 13:41:32.407451 2020] [ssl:emerg] [pid 72981] AH02311: Fatal error initialising mod_ssl, exiting. See /var/www/laggersec.org/log/error.log for more information
[Sun Mar 22 14:35:38.944945 2020] [suexec:notice] [pid 78824] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Mar 22 14:35:38.945970 2020] [ssl:emerg] [pid 78824] AH02311: Fatal error initialising mod_ssl, exiting. See /var/www/laggersec.org/log/error.log for more information
[Mon Mar 23 14:03:41.301190 2020] [core:notice] [pid 95150] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Mon Mar 23 14:03:41.310673 2020] [suexec:notice] [pid 95150] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Mar 23 14:03:41.311961 2020] [ssl:emerg] [pid 95150] AH01903: Failed to configure CA certificate chain!
[Mon Mar 23 14:03:41.311973 2020] [ssl:emerg] [pid 95150] AH02312: Fatal error initialising mod_ssl, exiting.
[Mon Mar 23 14:29:46.498804 2020] [core:notice] [pid 97660] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Mon Mar 23 14:29:46.500217 2020] [suexec:notice] [pid 97660] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Mar 23 14:29:46.501001 2020] [ssl:emerg] [pid 97660] AH01903: Failed to configure CA certificate chain!
[Mon Mar 23 14:29:46.501007 2020] [ssl:emerg] [pid 97660] AH02312: Fatal error initialising mod_ssl, exiting.
[Mon Mar 23 17:24:10.788302 2020] [core:notice] [pid 116365] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Mon Mar 23 17:24:10.789746 2020] [suexec:notice] [pid 116365] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Mar 23 17:24:10.790996 2020] [ssl:emerg] [pid 116365] AH01903: Failed to configure CA certificate chain!
[Mon Mar 23 17:24:10.791006 2020] [ssl:emerg] [pid 116365] AH02312: Fatal error initialising mod_ssl, exiting.
Is there any expert that could help me out?
I figured it out. I had to use SSLCACertificateFile directive instead of SSLCertificateChainFile directive. This was due to Go Daddy's cert not containing any Intermediate CA entities.
I cannot restart apache on CentOS. The results are below. I cannot locate a meaningful error to fix the issue.
Running service httpd start
Results in
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
Then running systemctl status httpd.service
Results in
httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2017-06-11 08:29:11 EDT; 15min ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 640 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 638 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=killed, signal=SEGV)
Main PID: 638 (code=killed, signal=SEGV)
Jun 11 08:29:11 server systemd[1]: Starting The Apache HTTP Server...
Jun 11 08:29:11 server systemd[1]: httpd.service: main process exited, code=killed, status=11/SEGV
Jun 11 08:29:11 server kill[640]: kill: cannot find process ""
Jun 11 08:29:11 server systemd[1]: httpd.service: control process exited, code=exited status=1
Jun 11 08:29:11 server systemd[1]: Failed to start The Apache HTTP Server.
Jun 11 08:29:11 server systemd[1]: Unit httpd.service entered failed state.
Jun 11 08:29:11 server systemd[1]: httpd.service failed.
And journalctl -xe
Results in
Jun 11 08:45:10 server systemd[1]: Starting The Apache HTTP Server...
-- Subject: Unit httpd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has begun starting up.
Jun 11 08:45:10 server systemd[1]: httpd.service: main process exited, code=killed, status=11/SEGV
Jun 11 08:45:10 server kill[691]: kill: cannot find process ""
Jun 11 08:45:10 server systemd[1]: httpd.service: control process exited, code=exited status=1
Jun 11 08:45:10 server systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit httpd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has failed.
--
-- The result is failed.
Jun 11 08:45:10 server systemd[1]: Unit httpd.service entered failed state.
Jun 11 08:45:10 server systemd[1]: httpd.service failed.
And from /etc/httpd/logs/error_log
[Sun Jun 11 08:49:33.214825 2017] [suexec:notice] [pid 761] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Jun 11 08:49:33.237392 2017] [auth_digest:notice] [pid 761] AH01757: generating secret for digest authentication ...
[Sun Jun 11 08:49:33.238036 2017] [lbmethod_heartbeat:notice] [pid 761] AH02282: No slotmem from mod_heartmonitor
PHP Fatal error: PHP Startup: apc_shm_create: shmget(0, 67108864, 914) failed: Invalid argument. It is possible that the chosen SHM segment size is higher than the operation system allows. Linux has usually a default limit of 32MB per segment. in Unknown on line 0
PHP Fatal error: PHP Startup: apc_shm_attach: shmat failed: in Unknown on line 0
I've spent a few hours trying to configure my Apache server to use SSL with no public IP, just localhost. I've created the certificate OK, I think (it has been like a crash course on black magic for me), and when I try tro access https://localhost, the browser says "Connected to localhost..." on the status line but just keeps loading forever. Here's a snippet from error_log:
[Fri Mar 27 22:03:39 2009] [info] Loading certificate & private key of SSL-aware server
[Fri Mar 27 22:03:39 2009] [info] Configuring server for SSL protocol
[Fri Mar 27 22:03:39 2009] [info] Loading certificate & private key of SSL-aware server
[Fri Mar 27 22:03:40 2009] [info] Configuring server for SSL protocol
everything seems to be OK there, but, meanwhile, at ssl_engine_log...
[Fri Mar 27 22:03:39 2009] [info] Init: Initializing OpenSSL library
[Fri Mar 27 22:03:39 2009] [info] Init: Seeding PRNG with 136 bytes of entropy
[Fri Mar 27 22:03:39 2009] [info] Init: Generating temporary RSA private keys (512/1024 bits)
[Fri Mar 27 22:03:39 2009] [info] Init: Generating temporary DH parameters (512/1024 bits)
[Fri Mar 27 22:03:39 2009] [info] Init: Initializing (virtual) servers for SSL
[Fri Mar 27 22:03:39 2009] [info] mod_ssl/2.0.61 compiled against Server: Apache/2.0.61, Library: OpenSSL/0.9.7i
[Fri Mar 27 22:03:39 2009] [warn] module php5_module is already loaded, skipping
[Fri Mar 27 22:03:39 2009] [info] Init: Initializing OpenSSL library
[Fri Mar 27 22:03:39 2009] [info] Init: Seeding PRNG with 136 bytes of entropy[Fri Mar 27 22:03:39 2009] [info] Init: Generating temporary RSA private keys (512/1024 bits)
[Fri Mar 27 22:03:40 2009] [info] Init: Generating temporary DH parameters (512/1024 bits)
[Fri Mar 27 22:03:40 2009] [info] Init: Initializing (virtual) servers for SSL
[Fri Mar 27 22:03:40 2009] [info] mod_ssl/2.0.61 compiled against Server: Apache/2.0.61, Library: OpenSSL/0.9.7i
[Fri Mar 27 22:03:40 2009] [notice] Digest: generating secret for digest authentication ...
[Fri Mar 27 22:03:40 2009] [notice] Digest: done
[Fri Mar 27 22:03:40 2009] [notice] Apache/2.0.61 (Unix) mod_ssl/2.0.61 OpenSSL/0.9.7l DAV/2 PHP/5.2.5 configured -- resuming normal operations
[Fri Mar 27 22:03:40 2009] [info] Server built: Jan 17 2008 17:33:42
[Fri Mar 27 22:03:40 2009] [emerg] (13)Permission denied: apr_proc_mutex_lock failed. Attempting to shutdown process gracefully.
[Fri Mar 27 22:03:40 2009] [emerg] (13)Permission denied: apr_proc_mutex_lock failed. Attempting to shutdown process gracefully.
...many more like these last two lines, until I finally stop the server...
[Fri Mar 27 22:03:43 2009] [info] removed PID file /usr/local/apache2/logs/httpd.pid (pid=8786)
[Fri Mar 27 22:03:43 2009] [notice] caught SIGTERM, shutting down
some googling about this permission denied and the apr_proc_mutex_lock failing hasn't yielded anything useful. Only some results relating to MPM and perchild option, but as they were old (years 2002 and 2003) and I don't really can draw any conclusions after reading them, I'm asking you if there is a way to overcome this problem. Well, first: what is actually the problem? Is there any kind of incompatibility between modules? Do I have to recompile something (please, Lord, not again, no)?
Thanks in advance.
Just be thankful you aren't using apache 1.3--it was way harder to get SSL running on that!
mod_ssl needs write permission on a couple files for it to work. Take a look at this setting and make sure apache has write access to the directory that file is in. For example, if says (for example):
SSLMutex file:/var/run/apache/ssl.mutex
You need to verify apache can write to /var/run/apache.
Almost all of these kinds of errors are usually some kind of permission error on the filesystem.