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.7 not answering on Windows Server 2012 |
|
| Author |
|
Tinchote
Joined: 12 Feb 2014
Posts: 2
|
 Posted: Wed 12 Feb '14 1:08 Post subject: Apache 2.4.7 not answering on Windows Server 2012 |
 |
|
So, here is my setup: a newly installed Windows Server 2012. The only software installed on it beyond the operating system is Apache 2.4.7 and PHP 2.4. The computer is in a LAN behind a router. The router tunnels port 80 to port 80 in this computer.
After I set up my website, everything was working perfectly: I could see the web pages from outside my LAN, PHP was executing, accesses were logged.
Then after a couple days, I could not open the pages from outside the LAN. From within the LAN, I could open them sometimes and sometimes they wouldn't.
Some facts:
- From within the server itself, I can open all pages.
- If I telnet to port 80 either from within the LAN or from outside, a few times the port would answer but wouldn't serve the GET request, while other times it just does not reply.
- Netstat shows port 80 binded to httpd.exe.
- If I make the router tunnel port 80 to another computer in the LAN, I can serve pages from this other computer, so it doesn't seem like the router is the problem.
- The server does not answer to vpn connect attempts either. It does open connections to Remote Desktop, however, even from outside the LAN (both ports tunnelled by the router).
- I have tried all this both with Windows Firewall activated and not activated. I have also checked the rules, and the only rule that mentions port 80 is the one for Apache, and is set to allow all.
- No error messages are reported in Apache logs.
- Restarting the server did not seem to make a difference.
I cannot make sense of all this. Any troubleshooting suggestion will be very welcome. |
|
| Back to top |
|
Steffen
Moderator
Joined: 15 Oct 2005
Posts: 3059
Location: Hilversum, NL, EU
|
| Posted: Wed 12 Feb '14 1:33 Post subject: |
|
|
Do you have in your config the following ?
AcceptFilter http none
AcceptFilter https none
EnableSendfile off
EnableMMAP off
Is advised with the kind of issue you have. |
|
| Back to top |
|
Tinchote
Joined: 12 Feb 2014
Posts: 2
|
| Posted: Wed 12 Feb '14 2:47 Post subject: |
|
|
| Steffen wrote: | Do you have in your config the following ?
AcceptFilter http none
AcceptFilter https none
EnableSendfile off
EnableMMAP off
Is advised with the kind of issue you have. |
Yes, I found that in some thread and I tried. Made no difference.
Something that I forgot to mention is these messages that appear in the error log (it is not obvious to me if they are actually reporting an error):
| Code: |
[Tue Feb 11 18:37:55.829173 2014] [core:notice] [pid 1256:tid 424] AH00094: Command line: 'C:\\Program Files\\Apache24\\bin\\httpd.exe -d C:/Program Files/Apache24'
[Tue Feb 11 18:37:55.831173 2014] [mpm_winnt:notice] [pid 1256:tid 424] AH00418: Parent: Created child process 3264
[Tue Feb 11 18:37:56.533257 2014] [mpm_winnt:notice] [pid 3264:tid 300] AH00354: Child: Starting 64 worker threads.
[Tue Feb 11 18:37:57.319352 2014] [mpm_winnt:notice] [pid 2492:tid 308] AH00364: Child: All worker threads have exited.
|
|
|
| Back to top |
|
Anaksunaman
Joined: 19 Dec 2013
Posts: 54
|
| Posted: Mon 17 Feb '14 10:36 Post subject: Apache 2.4.7 not answering on Windows Server 2012 |
|
|
The error.log data is generally consistent with normal start-up/shutdown messaging (e.g. there are no "errors" in what you posted -- these lines will attempt to be written to the error.log no matter what).
The only possibility of an error lies in the following line:
| Code: | [Tue Feb 11 18:37:56.533257 2014] [mpm_winnt:notice] [pid 3264:tid 300] AH00354: Child: Starting 64 worker threads.
[Tue Feb 11 18:37:57.319352 2014] [mpm_winnt:notice] [pid 2492:tid 308] AH00364: Child: All worker threads have exited. |
The line
| Code: | | [Tue Feb 11 18:37:57.319352 2014] [mpm_winnt:notice] [pid 2492:tid 308] AH00364: Child: All worker threads have exited. |
is usually printed during server shutdown. Given the timestamps in the log, it seems to indicate there might be a server immediately shutdown after start up.
Two potentially odd things in the error.log data you posted are:
A) there seems to be a missing "Parent: Received shutdown signal -- Shutting down the server." directive like in the following:
| Code: | [Tue Feb 11 00:47:14.449172 2014] [core:notice] [pid 1908:tid 376] AH00094: Command line: 'C:\\Programs\\Apache2.4\\bin\\httpd.exe -d C:/Programs/Apache2.4'
[Tue Feb 11 00:47:19.285181 2014] [mpm_winnt:notice] [pid 2764:tid 276] AH00354: Child: Starting 64 worker threads.
[Tue Feb 11 05:35:39.700155 2014] [mpm_winnt:notice] [pid 1908:tid 376] AH00422: Parent: Received shutdown signal -- Shutting down the server.
[Tue Feb 11 05:35:48.482657 2014] [mpm_winnt:notice] [pid 2764:tid 276] AH00364: Child: All worker threads have exited. |
B) the pid/tid for these lines don't match between them like so:
| Code: | [pid 2764:tid 276] AH00354: Child: Starting 64 worker threads.
[...]
[pid 2764:tid 276] AH00364: Child: All worker threads have exited. |
vs. your log
| Code: | [pid 3264:tid 300] AH00354: Child: Starting 64 worker threads.
[pid 2492:tid 308] AH00364: Child: All worker threads have exited. |
|
|
| Back to top |
|
|
|
|
|
|
