1 |
> +1 on Alan's hunch. I have not used Squid to comment on the specifics and |
2 |
> also Grant stated that another proxy gave him similar symptoms. From my |
3 |
> limited knowledge a proxy could be stalling because of cache configuration |
4 |
> problems, like running out fs space, or inodes and also running out of memory |
5 |
> if it has to process simultaneous requests from too many clients at a time. |
6 |
> If the problem also manifests when the clients are within the same subnet, |
7 |
> then this is unlikely to be a network issue. |
8 |
|
9 |
Which hunch was that? I snipped a lot above but I couldn't find it in there. |
10 |
|
11 |
It's just one user (me) and I've fiddled with the cache (including |
12 |
disabling it) and at least fs space and memory are good. |
13 |
|
14 |
> If all other causes are eliminated then a network related problem could be |
15 |
> associated with TCP Window Scaling - but this would primarily show up on the |
16 |
> transmission of larger files. This is why I initially asked if the problem |
17 |
> shows up on video/audio downloads rather than small web pages. |
18 |
> |
19 |
> It's probably OT describing this problem here (Google can do it much better) |
20 |
> but a quick test would show if this solves the problem: |
21 |
> |
22 |
> echo 0 > /proc.sys/net/ipv4/tcp_default_window_scaling |
23 |
> |
24 |
> Please check the man page because this key may have changed over time and |
25 |
> indeed it may not be a problem in later kernels who may have been coded so as |
26 |
> to compensate for dodgy routers. This will slow down the connection because a |
27 |
> smaller window size will be used, but there shouldn't be a problem of |
28 |
> oversized packets being dropped by a misconfigured router on the way. Shout |
29 |
> if you need more detail. |
30 |
|
31 |
I've tried all of these with no noticeable change: |
32 |
|
33 |
echo 0 > /proc/sys/net/ipv4/tcp_ecn |
34 |
echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc |
35 |
echo 0 > /proc/sys/net/ipv4/tcp_window_scaling |
36 |
|
37 |
Not that anyone here should bother to read it, but here's a link to my |
38 |
thread on the squid list where I tried all kinds of stuff: |
39 |
|
40 |
http://squid-web-proxy-cache.1019090.n4.nabble.com/squid-3-3-5-hangs-the-entire-system-td4660893.html |
41 |
|
42 |
I think at this point I'm hoping that putting the server's |
43 |
modem/router into bridged mode so it will respond to pings will clear |
44 |
this up. I think that's conceivable if the modem/router is also |
45 |
failing to return Fragmentation Needed since its MTU is 1492. Testing |
46 |
the proxy from within the server's LAN as you suggested in my other |
47 |
thread could also be informative. Please let me know if there's |
48 |
anything else I should try. |
49 |
|
50 |
- Grant |