[squid-users] connections from particular users sometimes get stuck
Eugene M. Zheganin
emz at norma.perm.ru
Tue Sep 27 17:13:17 UTC 2016
Hi.
I have a weird problem. I run a squid cache 3.5.19 on FreeBSD/amd64,
with about 300 active users, lots of authentication, external helpers
(yeah, it's usually the place when one starts to post configs, but let
me get to the point), and everything basically works just fine, but
sometimes one particular user (don't know, may be it's one particular
machine or some other entity) starts to have troubles. Usual trouble
looks like the following:
- around 299 users are working and authenticatiing just fine
- one particular user starts experiencing connection stucking: his
browser requests a web page, it starts to load and then some random
object on it blocks indefinitely.
- this happens every time on one machine, for the time given. This
machine is permanent for a given issue, until it's gone. Then it's some
another machine, and I cannot figure out the pattern.
- this machine may be locked in this malfuctioning state for days. This
state is usually cleared by the squid restart, or it may clear itself.
- after a month or so the issue appears on another machine. and it
persists on a new machine for quite some time.
On a l3 level this looks simple: browser requests an object, gets 407
answer, replies with proper credentials set and then this connection
goes indefinitely into a keepalived state: the squid and the browser
send keepalives to each other, but nothing happens other than
keepalives. User sees the spinning loader on a browser tab, and some
content inside the tab, depending on how many objects the browses has
received. In the same time new connections to squid are opening from
this machine just fine, and the basic connectivity is normal for both
the squid and the troubled machine. Furthermore, I'm sure that this
problem isn't caused by bottlenecks on the squid machine: because it
this way all the users would have eventually this problem, not only one.
In the same time these aren't bottlenecks on the user machine: while the
browser is stuck, other applications are working fine. If I switch the
proxy to a backup squid (on another server) this machine is able to
browse the internet.
I really need to solve this, but I have no idea where to start. The
error log show nothing suspicious.
The wireshark screen where the issue is isolated for one particular
connection can be found here -
https://gyazo.com/fdec1d9d7c31a75afc7d4676abb83d15 (it's really a simple
picture: TCP connection establishing, then GET -> 407 -> GET and bunch
of keepalives, not a rocket science).
Any ideas ?
Thanks.
Eugene.
More information about the squid-users
mailing list