| Author |
|
jmweb
Joined: 08 Jun 2017
Posts: 11
Location: USA, Charlotte
|
 Posted: Wed 29 Jan '25 15:20 Post subject: |
 |
|
I cannot get 2.4.63 to run. No error is written to the httpd log. I could only find the following through Window's Event Viewer:
| Code: |
Faulting application name: httpd.exe, version: 2.4.63.0, time stamp: 0x6790b2bc
Faulting module name: libcrypto-3-x64.dll, version: 3.4.0.0, time stamp: 0x6784d788
Exception code: 0xc0000005
Fault offset: 0x00000000002606c0
Faulting process id: 0xc20
Faulting application start time: 0x01db724eaef05a3f
Faulting application path: C:\WAMP\apache\bin\httpd.exe
Faulting module path: C:\WAMP\apache\bin\libcrypto-3-x64.dll
Report Id: ed483193-de41-11ef-aca5-08002778afeb
|
I downloaded httpd-2.4.63-250122-win64-VS17. My upgrade procedure is simple:
1) Unzip new version.
2) Stop httpd.
3) Move configuration files.
4) Start httpd.
This has worked for years. Please let me know what I can do on my end to troubleshoot. |
|
| Back to top |
|
tangent
Moderator
Joined: 16 Aug 2020
Posts: 354
Location: UK
|
| Posted: Wed 29 Jan '25 23:31 Post subject: |
|
|
Your eventlog error refers to libcrypto-3.x64.dll, so the problem appears to be OpenSSL related. However, I'm surprised nothing is reported in the Apache error log.
Apache 2.4.63 has been updated to use OpenSSL 3.4.0; previously at release 3.1.7, so quite a step change.
Since you say your upgrade procedure has worked for years, I suspect you've not reviewed/revised your OpenSSL configuration settings.
Chances are your Apache configuration is calling for a now deprecated OpenSSL feature, protocol or cipher, and needs revising. Take a look at https://ssl-config.mozilla.org if you need to rework your SSL configuration. Equally, check out various posts on this site from James Blond (search for "SSL ciphers" with named author), who is very knowledgeable on this subject. |
|
| Back to top |
|
jmweb
Joined: 08 Jun 2017
Posts: 11
Location: USA, Charlotte
|
| Posted: Thu 30 Jan '25 5:12 Post subject: |
|
|
| Thank you for pointing me in the right direction. Unfortunately, I still cannot get httpd to run. I went as far as commenting out all of my mod_ssl settings and just using the settings provided by ssl-config.mozilla.org. Is it possible that OpenSSL 3.4.0 is not compatible with my old Win 7 64bit box? I do have VS17 installed, obviously. |
|
| Back to top |
|
jmweb
Joined: 08 Jun 2017
Posts: 11
Location: USA, Charlotte
|
| Posted: Thu 30 Jan '25 6:21 Post subject: New Development |
|
|
I spun up a Win 10 Pro 64bit VM and simply moved my httpd installation folder containing the binaries and configuration files and it works as expected - easy!
It appears OpenSSL 3.4.0 is not compatible with Win 7 Pro 64bit. Should this finding be detailed on the downloads page?
As for my case, this is unfortunately an upgrade block since I have other software running that cannot upgrade away from Win 7 ATM.
Is there any way httpd 2.4.63 can be compiled with an older version of OpenSSL? |
|
| Back to top |
|
admin
Site Admin
Joined: 15 Oct 2005
Posts: 696
|
|
| Back to top |
|
timj
Joined: 30 Jan 2025
Posts: 3
Location: UK
|
| Posted: Thu 30 Jan '25 13:51 Post subject: |
|
|
I'm also seeing this problem but on my Win11 23H2 machine. It's intermittent and I can't reliably reproduce the issue. It seems to trigger most frequently at boot (I have Apache running as a service automatically at boot).
I've set LogLevel Debug today but haven't hit the issue yet to see if anything useful is recorded.
As this is an intermittent issue it may be a while before others start to encounter it.
Windows Event log entry looks almost identical to jmweb's:
| Code: | Faulting application name: httpd.exe, version: 2.4.63.0, time stamp: 0x6790b2bc
Faulting module name: libcrypto-3-x64.dll, version: 3.4.0.0, time stamp: 0x6784d788
Exception code: 0xc0000005
Fault offset: 0x00000000002606c0
Faulting process id: 0x0x1A20
Faulting application start time: 0x0x1DB72F56A1E83A1
Faulting application path: C:\DATA\web\apps\apache_2_4\bin\httpd.exe
Faulting module path: C:\DATA\web\apps\apache_2_4\bin\libcrypto-3-x64.dll |
I'm curious as to why some of the values are double prefixed with 0x0x. That doesn't seem right.
I'll post again when I next see a crash. |
|
| Back to top |
|
admin
Site Admin
Joined: 15 Oct 2005
Posts: 696
|
| Posted: Thu 30 Jan '25 14:34 Post subject: |
|
|
| Running PHP as module ? |
|
| Back to top |
|
timj
Joined: 30 Jan 2025
Posts: 3
Location: UK
|
| Posted: Thu 30 Jan '25 15:00 Post subject: |
|
|
| Via mod_fcgid. |
|
| Back to top |
|
Otomatic
Joined: 01 Sep 2011
Posts: 226
Location: Paris, France, EU
|
| Posted: Thu 30 Jan '25 15:48 Post subject: |
|
|
| timj wrote: | | I'm also seeing this problem but on my Win11 23H2 machine. It's intermittent and I can't reliably reproduce the issue. It seems to trigger most frequently at boot (I have Apache running as a service automatically at boot) |
You have no control over when the Apache service starts. The Apache service may well start before everything it needs is loaded.
It would be better to set the Apache service to "Automatic (Delayed start)". |
|
| Back to top |
|
timj
Joined: 30 Jan 2025
Posts: 3
Location: UK
|
| Posted: Thu 30 Jan '25 16:09 Post subject: |
|
|
I rebooted and saw the same issue again.
Below is the entirety of the error.log generated (I cleared it before reboot):
| Code: | [Thu Jan 30 13:14:26.481719 2025] [ssl:info] [pid 6872:tid 404] AH01883: Init: Initialized OpenSSL library
[Thu Jan 30 13:14:26.486752 2025] [ssl:debug] [pid 6872:tid 404] ssl_engine_init.c(364): AH01886: OpenSSL has FIPS mode disabled
[Thu Jan 30 13:14:26.486752 2025] [ssl:info] [pid 6872:tid 404] AH01887: Init: Initializing (virtual) servers for SSL
[Thu Jan 30 13:14:26.576794 2025] [ssl:info] [pid 6872:tid 404] AH01876: mod_ssl/2.4.63 compiled against Server: Apache/2.4.63, Library: OpenSSL/3.4.0
[Thu Jan 30 13:14:26.576794 2025] [http2:debug] [pid 6872:tid 404] mod_http2.c(112): AH03089: initializing post config dry run
[Thu Jan 30 13:14:26.701715 2025] [ssl:info] [pid 6872:tid 404] AH01883: Init: Initialized OpenSSL library
[Thu Jan 30 13:14:26.701715 2025] [ssl:debug] [pid 6872:tid 404] ssl_engine_init.c(364): AH01886: OpenSSL has FIPS mode disabled
[Thu Jan 30 13:14:26.701715 2025] [socache_shmcb:debug] [pid 6872:tid 404] mod_socache_shmcb.c(414): AH00821: shmcb_init allocated 512000 bytes of shared memory
[Thu Jan 30 13:14:26.701715 2025] [socache_shmcb:debug] [pid 6872:tid 404] mod_socache_shmcb.c(428): AH00822: for 511944 bytes (512000 including header), recommending 32 subcaches, 88 indexes each
[Thu Jan 30 13:14:26.701715 2025] [socache_shmcb:debug] [pid 6872:tid 404] mod_socache_shmcb.c(465): AH00824: shmcb_init_memory choices follow
[Thu Jan 30 13:14:26.701715 2025] [socache_shmcb:debug] [pid 6872:tid 404] mod_socache_shmcb.c(467): AH00825: subcache_num = 32
[Thu Jan 30 13:14:26.701715 2025] [socache_shmcb:debug] [pid 6872:tid 404] mod_socache_shmcb.c(469): AH00826: subcache_size = 15992
[Thu Jan 30 13:14:26.701715 2025] [socache_shmcb:debug] [pid 6872:tid 404] mod_socache_shmcb.c(471): AH00827: subcache_data_offset = 2128
[Thu Jan 30 13:14:26.701715 2025] [socache_shmcb:debug] [pid 6872:tid 404] mod_socache_shmcb.c(473): AH00828: subcache_data_size = 13864
[Thu Jan 30 13:14:26.701715 2025] [socache_shmcb:debug] [pid 6872:tid 404] mod_socache_shmcb.c(475): AH00829: index_num = 88
[Thu Jan 30 13:14:26.701715 2025] [socache_shmcb:info] [pid 6872:tid 404] AH00830: Shared memory socache initialised
[Thu Jan 30 13:14:26.701715 2025] [ssl:info] [pid 6872:tid 404] AH01887: Init: Initializing (virtual) servers for SSL |
And the resulting entry in the Windows Event Viewer:
| Code: | Faulting application name: httpd.exe, version: 2.4.63.0, time stamp: 0x6790b2bc
Faulting module name: libcrypto-3-x64.dll, version: 3.4.0.0, time stamp: 0x6784d788
Exception code: 0xc0000005
Fault offset: 0x00000000002606c0
Faulting process id: 0x0x1AD8
Faulting application start time: 0x0x1DB7318E1BC875B
Faulting application path: C:\DATA\web\apps\apache_2_4\bin\httpd.exe
Faulting module path: C:\DATA\web\apps\apache_2_4\bin\libcrypto-3-x64.dll |
This was logged at 2025-01-30T13:14:27.1945114Z so the crash happened less than half a second after the last log entry.
I'll try stripping back my config to the bare minimum to see if I can narrow this down. But at this point it really does seem like an issue in OpenSSL 3.4.0.
| Otomatic wrote: | | timj wrote: | | I'm also seeing this problem but on my Win11 23H2 machine. It's intermittent and I can't reliably reproduce the issue. It seems to trigger most frequently at boot (I have Apache running as a service automatically at boot) |
You have no control over when the Apache service starts. The Apache service may well start before everything it needs is loaded.
It would be better to set the Apache service to "Automatic (Delayed start)". |
You have limited control, e.g. sc config [service name] depend=...
I haven't had problems with this in >15 years of running Apache instances on multiple Windows servers with automatic service startup. Clearly something is different here. Whether that difference is a bug, an intended change, or a side effect, is what I'm trying to understand.
I'll also note that I've encountered this error at least once when trying to start the service manually. |
|
| Back to top |
|
Steffen
Moderator
Joined: 15 Oct 2005
Posts: 3101
Location: Hilversum, NL, EU
|
|
| Back to top |
|
