hey dude, on your squid box, open up a terminal and do this to see the
log file in real time,
tail -f /var/log/squid3/access.log
or
tail -f /var/log/squid/access.log
depending on where your logs are of course..
then u can watch the logs as they come in, and pinpoint your error, its
a little old timey trick that works good for debugging
On Sat, 2012-01-21 at 19:09 +1300, Amos Jeffries wrote:
> On 21/01/2012 7:07 a.m., Jorge Bastos wrote:
> > Howdy mates,
> > I have a problem with an website, not that I really ASUS... in fact their
>
> > The following error was encountered while trying to retrieve the URL:
> > http://www.asus.com/
> >
> > Read Error
> >
> > The system returned: (104) Connection reset by peer
>
> Start with figuring out which server is failing. Your Squid access.log
> entry for the request should contain the IP address of the server which
> was contacted to fetch the response.
>
> Read Error means the connection got setup at the TCP level but then no
> data packets for that connection got through. Usually PMTU black hole
> problems, Window Scaling problems, ECN problems. TCP and ICMP level
> things like that breaking the packet management.
>
> Amos
Received on Sat Jan 21 2012 - 14:09:29 MST
This archive was generated by hypermail 2.2.0 : Sat Jan 21 2012 - 12:00:02 MST