Search squid archive

Re: Connection timeout

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2013-11-19 04:18, adamso wrote:
Hi,

This is the content of my cache.log
2013/11/18 13:41:04 kid1| local=192.168.0.101:3128 remote=192.168.0.19:49602
FD 95 flags=1: read/write failure: (113) No route to host

Network connection between proxy and client broke (network cable unplugged, wireless disconnected, or something to similar effect).


2013/11/18 13:50:06 kid1| local=192.168.0.101:3128 remote=192.168.0.21:53576
FD 66 flags=1: read/write failure: (32) Broken pipe

Client disconnected. Similar to the above.


2013/11/18 14:53:21 kid1| local=192.168.0.101:3128 remote=192.168.0.21:49499
FD 106 flags=1: read/write failure: (110) Connection timed out

Exactly so. "connection too slow" is both the problem and what the message means.


<elided duplicates>


There is a problem?? What does it mean?
My connection become sometimes too slow.


Exactly so. "connection too slow" is both the problem and what the message means.

It can happen in a number of ways:
* web browser "Happy Eyeballs" mechanism
* network congestion
* buffer bloat
* wireless interference (if any of the links are wireless, Wifi etc)
* overloaded proxy not responding fast enough to keep the cleint from disconnecting
* broken firewall somewhere
* broken HTTP middleware
* read/write timout values configured too low for your network requirements


Note these are *all* generic networking problems. Other than the small possibility of misconfiguration there is nothing particualrly related to Squid in the reasons for those errors happening.

Amos





[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux