Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: Apache 2.4 Problems in Windows x86 |
|
| Author |
|
BillAngus
Joined: 20 May 2012
Posts: 7
Location: Maple Ridge, BC Canada
|
 Posted: Sun 26 May '13 21:47 Post subject: Apache 2.4 Problems in Windows x86 |
 |
|
a couple of problems are sending me back to version 2.2 until these may be resolved. This is the most vexing issue. Initially the whole system works fine.
(1) After a while of operation the server stops working ... Error log looks as below...
...
[Sun May 26 12:23:42.649103 2013] [mpm_winnt:notice] [pid 1356:tid 352] AH00424: Parent: Received restart signal -- Restarting the server.
[Sun May 26 12:23:43.616304 2013] [mpm_winnt:notice] [pid 1356:tid 352] AH00455: Apache/2.4.4 (Win64) OpenSSL/1.0.1e PHP/5.4.14 configured -- resuming normal operations
[Sun May 26 12:23:43.616304 2013] [mpm_winnt:notice] [pid 1356:tid 352] AH00456: Server built: Feb 22 2013 22:08:37
[Sun May 26 12:23:43.616304 2013] [core:notice] [pid 1356:tid 352] AH00094: Command line: 'c:\\apache2\\bin\\httpd.exe -d C:/Apache2'
[Sun May 26 12:23:43.616304 2013] [mpm_winnt:notice] [pid 1356:tid 352] AH00418: Parent: Created child process 3840
[Sun May 26 12:23:44.443106 2013] [mpm_winnt:notice] [pid 3840:tid 240] AH00354: Child: Starting 64 worker threads.
[Sun May 26 12:23:44.458706 2013] [mpm_winnt:warn] [pid 3840:tid 1596] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Sun May 26 12:23:44.458706 2013] [mpm_winnt:warn] [pid 3840:tid 1596] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Sun May 26 12:23:44.458706 2013] [mpm_winnt:warn] [pid 3840:tid 1596] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
[Sun May 26 12:24:09.621550 2013] [mpm_winnt:warn] [pid 3840:tid 1596] (OS 64)The specified network name is no longer available. : AH00341: winnt_accept: Asynchronous AcceptEx failed.
...
[NOTE THE RESTART OF APACHE WHICH IS REQUIRED TO KEEP THE SERVER OPERATIONAL] |
|
| Back to top |
|
Steffen
Moderator
Joined: 15 Oct 2005
Posts: 3092
Location: Hilversum, NL, EU
|
| Posted: Sun 26 May '13 21:54 Post subject: |
|
|
Be sure you have in httpd.conf:
For 2.2:
Win32DisableAcceptEx
EnableSendfile off
EnableMMAP off
For 2.4:
AcceptFilter http none
AcceptFilter https none
EnableSendfile off
EnableMMAP off
Steffen |
|
| Back to top |
|
BillAngus
Joined: 20 May 2012
Posts: 7
Location: Maple Ridge, BC Canada
|
| Posted: Mon 27 May '13 5:49 Post subject: |
|
|
THANKS Stefan - the best  |
|
| Back to top |
|
cjv
Joined: 29 Jun 2013
Posts: 1
Location: new york, ny
|
| Posted: Sat 29 Jun '13 23:36 Post subject: |
|
|
| I am extremely grateful for this answer, Steffen- I was losing my mind. Interestingly, at least to me, the pages were rendering fine in IE10 but not in Chrome. I was pulling what few remaining hairs I have out. |
|
| Back to top |
|
bberndt
Joined: 13 Aug 2013
Posts: 5
Location: USA
|
| Posted: Thu 15 Aug '13 17:58 Post subject: |
|
|
Why is this? Can I get some background on this, please?
I had it happen to me, on the first server I installed Apache 2.4.6, instead of 2.2.22.
The work around worked fine for me. In the past (with the 2.2.22 installer version of Apache win32, I leave the httpd.conf file pretty much alone, and just add my include directive, that points to a conf file that has all my mod_jk stuff in it.
Using Apache 2.4.6, win32, and mod_jk x86 to Tomcat, on Win2k8 R2. |
|
| Back to top |
|
Steffen
Moderator
Joined: 15 Oct 2005
Posts: 3092
Location: Hilversum, NL, EU
|
|
| Back to top |
|
bberndt
Joined: 13 Aug 2013
Posts: 5
Location: USA
|
| Posted: Thu 15 Aug '13 20:18 Post subject: |
|
|
I suppose I could have run into this, and not known it. I just checked a site that had weird problems last week, running Apache 2.2, and this error was in the error log, though nowhere near as often as this new 2.4 site I set up.
These links you point out, mention some performance loss with these work-arounds. That slightly concerns me... |
|
| Back to top |
|
|
|
|
|
|
