"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:
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:
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

On Mon, Jan 11, 2016 at 10:32 PM, Jim Walls <j...@k6ccc.org <mailto:j...@k6ccc.org>> wrote:

    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:
    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
    j...@k6ccc.org <mailto:j...@k6ccc.org>


-- 73
    -------------------------------------
    Jim Walls - K6CCC
    j...@k6ccc.org <mailto:j...@k6ccc.org>
    Ofc:818-548-4804 <tel:818-548-4804>
    http://members.dslextreme.com/users/k6ccc/
    AMSAT Member 32537 - WSWSS Member 395




--
73
-------------------------------------
Jim Walls - K6CCC
j...@k6ccc.org
Ofc:  818-548-4804
http://members.dslextreme.com/users/k6ccc/
AMSAT Member 32537 - WSWSS Member 395


--
73
-------------------------------------
Jim Walls - K6CCC
j...@k6ccc.org
Ofc:  818-548-4804
http://members.dslextreme.com/users/k6ccc/
AMSAT Member 32537 - WSWSS Member 395

Reply via email to