Connection reset by peer errors

Hi,

Probably an admin can solve this problem. I get lots of "Connection reset by peer" errors (mostly at peak hours) here in my country and that happens only on digitalpoint. I guess you have set the Apache "Timeout" config directive to a very small value. If that is right, can you please increase the "Timeout" value a little higher? Apache terminates connections if that timeout value reached before the receipt of a packet/ACK. On high latency wireless connections the delay can be quite long and we get several seconds of delay here on peak hours. If you can raise Timeout value to a few more seconds, that may solve this problem.

Thanks,
Cybernaut.

 

dunno...works fine over here.........

 

It works fine over dialup/dsl for me too. It only throws errors on my wireless connection whose latency is quite high, though the connection speed is 2 times the normal dialup most of the time. I expect, other wireless subscribers may also be having same problem. You need to have some idea of network latency and Apache's Timeout setting to better understand this.

 

mikey, thanks for the link. But I reckon that is not the same problem. I am talking about DP connection resets, not slow load times. Even if the load time is high, it does complete the page loading on dsl/dialup most of the time (at least for me). But, when I am on wireless, it terminates the connection in between page loading and some times just when the page loading already almost finished that causes firefox to discard all the loaded page and bring up an error. That annoys too much. Sometimes I have to try more than twice to fully load the page.

Another way to distinguish between the two problems is that you just open DP through a web based proxy. You wont get any error at all. Even if it takes some time load (now a days), it does load fully. I had sometimes to resort to a web based proxy to load DP. This is because server to server connections have very little latency and Apache does not drops connections.

I forgot to say that if DP's Apache servers work behind some frontend squids then it is squids' timeout settings that need to be relaxed.

Cybernaut.

 

I get the error too....

Shawn is aware of it- thank you!