Re: [squid-users] (104) connection reset by peer on heavy saturated network

Hi

Is a Squid (browser-generated error page) on Squid 3.3.8 running on
Debian 7 with a mostly default configuration. I'm using http intercept
now but before I had similar problems running squid 2.7 without
interception.

2014-06-05 5:46 GMT+02:00 Amos Jeffries <squid3_at_treenet.co.nz>:
>
> On 5/06/2014 4:08 a.m., Santiago GOMEZ wrote:
> > Hi
> >
> > In my office we are getting al lot of "(104) connection reset by peer"
> > I'm 90% sure our problem is the saturation of the network because
> > during lunch we don't get a single (104) connection reset by peer
> > error and if I monitor the network is when user use all of our upload
> > speed when we get 104 error all the time.
> >
> > Unfortunately, we have to wait for a few months until our ISP upgrades
> > our area speed.
> >
> > My question is if there is something I can try to do so squid don't
> > show so many errors. I prefer that it stays loading a website for 10
> > seconds than showing the message.
> >
> > Regards,
> >
>
> What Squid version?
>
> What configuration?
>
> What is the "peer" being talked about?
> Squid (browser-generated error page), or
> the upstream web servers (squid-generated error page)?
>
> Amos
>
Received on Thu Jun 05 2014 - 07:36:26 MDT