DevHeads.net

Apache stops serving pages

I have Apache 2.4.12 running on a 64 bit Windows Server 2012 R2
installation that periodically just stops serving web pages. Usually it
will start working after an hour or two, or if I'm in a position to remote
into the server I can restart the service using the Apache Service Monitor,
and normally get it to start without waiting. There is absolutely nothing
in the error or access logs. I have not seen anything that seems to relate
in the Windows logs either. I thought it might be having a firewall
(either Windows or router), but last time it stopped, while remoted into
the server, I brought up Firefox and tried to access a web page or two. I
get the browser error that the web server is not responding (or something
along that line). That should eliminate the router, or Windows firewall I
would think. As soon as I restart the Apache service, both Firefox on the
server and on a remote computer are able to access pages.

The server gets restarted every Friday afternoon, and last Friday Apache
stopped within a couple hours. Problem happen anywhere from a few hours
to several days apart. This is a very plain vanilla server that is serving
three Virtual Hosts (all are affected at the same time), with no dynamic
content - just plain old html

Any good ideas of a cause or where to start looking?

Jim Walls
<a href="mailto: ... at k6ccc dot org"> ... at k6ccc dot org</a>

Comments

Re: Apache stops serving pages

By Jim Walls at 01/11/2016 - 23:32

I asked the question below about my Apache server stopping serving
pages. Since then, the server has continued to stop serving pages
periodically, and is getting more frequent. A couple days ago,
wondering if there could be something competing for the IP port, I
changed the port from 81 to 8180, and then updated to port forwarding in
the router. I really had no reason to believe that port 81 was getting
any other activity, but it was an easy test. This did not make any
difference. Today I changed the error log level to debug to see if
anything showed up. Since that time, the server has stopped three more
times. In each case, I remoted into the server, and again was not able
to access any web pages from a web browser on the server. As soon as I
restarted Apache, it started working correctly. Looking at the error
logs, there is absolutely nothing to indicate a problem. Similarly, the
access log only showed that there was no activity from the time it
stopped serving pages, until I restarted the server, and then normal
activity.

I'm running out of ideas.

Anybody else?

Jim Walls

On 1/5/2016 11:05, Jim Walls wrote:

Re: Apache stops serving pages

By Yann Ylavic at 01/12/2016 - 04:04

On Tue, Jan 12, 2016 at 4:32 AM, Jim Walls < ... at k6ccc dot org> wrote:
Did you try Kevin's proposal, that is :
AcceptFilter http none
AcceptFilter https none
?

Regards,
Yann.

Re: Apache stops serving pages

By Jim Walls at 01/12/2016 - 12:40

Yann Ylavic asked: > Did you try Kevin's proposal, that is :

I don't remember seeing that message, so no I didn't.

However, If that was causing a problem, I would think that after setting
the error log to debug level, I would have seen it in the error log.

Jim

Re: Apache stops serving pages

By Yann Ylavic at 01/12/2016 - 12:48

On Tue, Jan 12, 2016 at 5:40 PM, Jim Walls < ... at k6ccc dot org> wrote:
Not necessarily because httpd won't see any request unless "delivered"
by the OS accept filters.
This is worth a try IMHO.

Regards,
Yann.

Re: Apache stops serving pages

By Jim Walls at 01/12/2016 - 12:59

Thanks for the more detailed answer. I was not familiar with the
AcceptFilter command. Since it was in Apache, I assumed (incorrectly) that
it was controlling filtering in Apache. I did a Google search and quickly
found that it is actually controlling Winsock, so now it makes sense that
it would not show up in the Apache error log.

Learn something new every day! I kind of dislike making multiple changes
to resolve a problem because then you may not know which one solved the
problem. Even if the change to 32 bit fixed the issue, I will add this in
a week or two cause it does sound like a good idea!

Jim

Not necessarily because httpd won't see any request unless "delivered"
by the OS accept filters.
This is worth a try IMHO.

Regards,
Yann.

Re: Apache stops serving pages

By Eric Covener at 01/12/2016 - 12:42

On Tue, Jan 12, 2016 at 11:40 AM, Jim Walls < ... at k6ccc dot org> wrote:
Not really.

Re: Apache stops serving pages

By Yehuda Katz at 01/12/2016 - 00:17

Are you using a 64-bit version of Apache or a 32-bit version? Where did you
download it?
I often have issue with the 64-bit Windows builds, so I usually stick to
the 32-bit builds from Apache Lounge.

- Y

Re: Apache stops serving pages

By Jim Walls at 01/12/2016 - 00:56

It is the 64 bit version (using VC11) from Apache Lounge. I can
certainly try it from 32 bit versions easily enough.

On 1/11/2016 20:17, Yehuda Katz wrote:

Re: Apache stops serving pages

By Jim Walls at 01/12/2016 - 02:01

"Upgraded" from 64 bit 2.4.12 (using VC11) to 32 bit 2.4.18 (using
VC14). Running after the upgrade. We'll see what it does...

Jim

On 1/11/2016 20:56, Jim Walls wrote:

Re: Apache stops serving pages

By Lester Caine at 01/12/2016 - 03:43

On 12/01/16 06:01, Jim Walls wrote:
I have a system that has run for many years on local intranets and was
being served by windows 2k and XP machines which were essentially 32bit
set-ups. Moving to W7 the replacement machines were inevitably
configured 64bit and so the obvious action was to add 64 bit server
code, but the day in day out reliability disappeared. Did try a 32bit
stack on the 64bit windows, but are now running 32bit windows as well.
Of cause we were told that we should be using server versions of windows
for this, but these machines manage perhaps 1% active time and the only
reason not to use 'virtual' servers on some other hardware is to
maintain sub second responses when doing things like printing a ticket
or receipt. ( How many of you have experienced the 30 second delay
waiting for windows to process a network print request after hitting the
finish link on a session. Very annoying for staff and customers when
there is a queue at the reception desk! )

Where we have moved to a Linux based stack things have been even more
responsive, back to the 24/7 stability that W2k and NT4 provided and
even smaller percentages on the active working times :)

Re: Apache stops serving pages

By Jim Walls at 01/12/2016 - 12:49

Personally I loved windows 2K. I had several user PCs running 2K Pro at
home, and ran the computer I used as a server under 2K Server for almost a
decade until it died a little over a year ago. Only reason I replaced it
was because it died - leaking caps on the mother board. I was given a 64
bit Dell server that I loaded up with Server 2012 R2 and like you it seemed
reasonable to install 64 bit Apache.

It's now been about 12 hours since I "upgraded" to a 32 bit version and so
far it's stable. I won't really call it fixed for at least a week, but
based on the recent track record, this is doing pretty good. I will be
taking the server down this weekend for an hour or two for it's annual dust
cleaning, and I'm going to add some RAM to it. And depending on how much
money is left after today's bill paying (today is payday for me), I might
increase replace the hard drives in the data RAID array to increase
capacity...

Jim

I have a system that has run for many years on local intranets and was
being served by windows 2k and XP machines which were essentially 32bit
set-ups. Moving to W7 the replacement machines were inevitably
configured 64bit and so the obvious action was to add 64 bit server
code, but the day in day out reliability disappeared. Did try a 32bit
stack on the 64bit windows, but are now running 32bit windows as well.
Of cause we were told that we should be using server versions of windows
for this, but these machines manage perhaps 1% active time and the only
reason not to use 'virtual' servers on some other hardware is to
maintain sub second responses when doing things like printing a ticket
or receipt. ( How many of you have experienced the 30 second delay
waiting for windows to process a network print request after hitting the
finish link on a session. Very annoying for staff and customers when
there is a queue at the reception desk! )

Where we have moved to a Linux based stack things have been even more
responsive, back to the 24/7 stability that W2k and NT4 provided and
even smaller percentages on the active working times :)

Re: Apache stops serving pages

By Kev at 01/05/2016 - 16:44

Hi Jim

We had similar problems.

Check this site as the solution might work for you:
<a href="http://superuser.com/questions/516030/apache-2-4-on-windows-responds-slowly-hangs-when-serving-some-dynamic-pages" title="http://superuser.com/questions/516030/apache-2-4-on-windows-responds-slowly-hangs-when-serving-some-dynamic-pages">http://superuser.com/questions/516030/apache-2-4-on-windows-responds-slo...</a>

Regards
Kev