Why does Apache stop serving one file after I request another?
Backing up a step: Googling “an established connection was aborted by the software in your host machine” reveals a couple of things: 1. Pretty much everyone agrees that the “software” here is WinSock, the Windows TCP/IP stack. 2. The Windows error number corresponding to this message is 10053. There is a wealth of forum material off a “10053 Windows error” search. 3. MSDN is next to no help. 4. Assorted notes: – “10053 errors are actually quite rare usually.” – One possible cause is the premature termination of the server. – Another is a virus check error. – “This error can occur when the local network system aborts a connection, such as when WinSock closes an established connection after data retransmission fails (receiver never acknowledges data sent on a datastream socket). Possibly due to a data transmission timeout or protocol error.” – An interesting solution to a 10053 – the guy reconfigured his network c
This is almost certainly your firewall; it sounds as if your firewall is maintaining a single record of a machine that’s allowed to use the mapped port to your webserver, and when a second machine tries to use the port, then the firewall gives the second machine the mapped connection. You can verify this by cutting the firewall out of the equation, at least temporarily; the easiest way is to put three machines on the local network (behind the firewall), #1 being the webserver and #2 and #2 being clients. Start a download from #2, and then start a download from #3. If it works fine, then it’s your firewall. To expand a bit, Ciscos in NAT mode maintain total separation of the outside and inside network, and then create a translation table that establishes short-term links between the two. When a machine on the outside network tries to reach a machine on the inside network, the Cisco checks its rules governing such access, and if the machine’s request matches the rules, then an entry is c
maschnitz: I’m not sure how one would alternately verify or eliminate your first two points. That said, access.log was showing the request, but with only a portion of the total bytes served. I did notice, however, that Apache threw a warning into error.log during my last attempt:[info] (OS 10053)An established connection was aborted by the software in your host machine. : core_output_filter: writing data to the networkboaz: I’m using a Cisco 678 router in NAT mode with everything but the essentials filtered. Portscanning my IP from the outside shows only the ports I opened for Apache and BitTorrent (no torrents running at the moment.) I’ve never run into similar failures during either upload or download of files to/from remote machines, so I’m leaning away from a straight-up connectivity issue. The second request is served without incident.
BTW, One possible solution to all this is to replace a piece of the system, one a time, until it works: 1. Swap out the firewall with a friend’s firewall. 2. Try simulating your application using Apache 1.3 on the same machine 3. Swap network cards. 4. Install Apache 2 on a second machine and retry. 5. Install Apache 2 on an XP machine and retry. 6. Take the entire setup over to a friend’s house or to work, reconfigure the networking, and retry. etc. A very work-intensive and sometimes impossible task, but it will eventually get the job done. I think #1 in particular is worth the effort at this point.
“An established connection was aborted by the software in your host machine” == “some other program next to me killed it”. That means something in the kernel on the box, or something with kernel-level access, killed the connection. I’m guessing it’s a virus checker or a software firewall. Try turning all such things off. See if it goes away.
