[plug] Squid error 113 no route to host

[Paul Baumgarten]

I really should have mentioned this earlier but the problem is only a new
one that started occuring when I rebuilt our Internet Gateway (using RH 5.2
distro).  The squid config is _exactly_ the same as it was on the old
machine but it is since this change that the 113 errors started.  I only
just noticed that the new install changed our squid from 1.1.10 to 1.1.22 -
I can't imagine this to be an issue but just in case I have just downloaded
2.2.STABLE4 and will install it over the weekend.  If this doesn't stop the
errors I am out of ideas.  In regards to our bandwidth (mentioned below) it
hasn't changed - we had and still do have 128 ISDN - yet the errors did not
occur before.  If any one else has any ideas I'd love to hear them as it has
got me baffled.

Paul Baumgarten (email: paul at kcc.wa.edu.au)
Information Systems Manager
Kingsway Christian College
157 Kingsway, Landsdale, WA, 6065
Ph: +61 8 9409 7078
Fx: +61 8 9409 6179

----- Original Message -----
From: John Breen <john.breen at unitedconstruction.com.au>
To: <plug at linux.org.au>
Sent: Friday, August 27, 1999 11:17 AM
Subject: RE: [plug] Squid error 113 no route to host


> Sounds like it might be related to the bandwidth of your connection.  That
> is, too many requests are happening over the connection at once, and it
> can't handle the amount of data.
>
> Effectively, SQUID isn't finding the site within a short enough time.  You
> can probably get around it by getting more bandwidth.
>
> Just a guess though.
>
> Cheers,
>
>
> John
>
> John Breen
> Programmer
> United Construction Pty Ltd
>
> (08) 9499-0472
> 0413-462-818
> john.breen at unitedconstruction.com.au
>
>
>
>
> -----Original Message-----
> From: Paul Baumgarten [SMTP:paul at kcc.wa.edu.au]
> Sent: Friday, August 27, 1999 11:13 AM
> To: plug at linux.org.au
> Subject: Re: [plug] Squid error 113 no route to host
>
> It only happens when there are quite a few people accessing the 'net
> at once
> (say over 10 or 15).  During these times it appears for most sites
> that
> aren't already cached by squid.  During "quieter" periods it doesn't
> occur.
>
> Paul Baumgarten (email: paul at kcc.wa.edu.au)
> Information Systems Manager
> Kingsway Christian College
> 157 Kingsway, Landsdale, WA, 6065
> Ph: +61 8 9409 7078
> Fx: +61 8 9409 6179
>
> ----- Original Message -----
> From: Buddrige, David <david.buddrige at mitswa.com.au>
> To: <plug at linux.org.au>
> Sent: Friday, August 27, 1999 10:46 AM
> Subject: RE: [plug] Squid error 113 no route to host
>
>
> > This was posted to Dejanews
> >
> >          > i have following problem when i would like to reach
> some sites.
> >          > ----------------------------------------------------
> ERROR  The
> >          > requested URL could not be retrieved  While trying to
> retrieve
> >          > the URL: http://www.ripe.net/cgi-bin/whois  The
> following error
> >          > was encountered:       Connection Failed  The system
> returned:
> >          > (113) No route to host  The remote host or network may
> be down.
> >          > Please try the request again.
> ---------------------------------
> >          > --------------------------------------  what must i
> configure
> >          > so that this will work?  greetings horst
> >
> >          'No route to host' means that there is  no way for data
> to get
> >          from your computer to the web site. Unless this happens
> with
> >          all sites, then the problem lies with the web site that
> you
> >          can't access, or with the one of the computers inbetween.
> >
> >          --
> >
> >
> > So thus, the question comes down to: is this happening at all
> sites?  If
> it
> > is happening at _all_ sites, then there must be a problem with the
> link
> > between you and the internet.
> >
> > Sometimes this error occurs when there is a problem with the link
> between
> > Australia and the rest of the world, in which case Aussie sites
> work ok,
> but
> > non-Aussie sites produce this error.
> >
> > Alternately, specific sites may have this problem, meaning that
> the part
> of
> > the internet they are on is disconnected (temporarily) from that
> part of
> the
> > internet to which your server is connected...
> >
> > cheers
> >
> > David Buddrige... 8-)
> > > -----Original Message-----
> > > From: Paul Baumgarten [SMTP:paul at kcc.wa.edu.au]
> > > Sent: Friday, August 27, 1999 10:00 AM
> > > To: Perth Linux Users Group
> > > Subject: [plug] Squid error 113 no route to host
> > >
> > > I am seeking enlightenment on the meaning, cause and resolution
> of squid
> > > generated error 113 - No route to host.
> > >
> > > Due to the fact that it mainly occurs during busy periods, such
> as if I
> > > have
> > > a big download happening, I think it has something to do with
> squid
> coping
> > > under load... maybe some sort of time out issue or some other
> such
> issue.
> > >
> > > If anyone knows of the cause of this and how I can resolve it I
> would
> > > appreciate hearing about it as the Squid FAQ doesn't mention a
> word
> about
> > > it.
> > >
> > > >ERROR
> > > >The requested URL could not be retrieved
> > >
>
> >-------------------------------------------------------------------------
> > > --
> > > -----
> > > >While trying to retrieve the URL: <someplace>
> > > >The following error was encountered:
> > > >Connection Failed
> > > >The system returned: (113) No route to host
> > > >This means that: The remote site or server may be busy or down.
> Please
> > > try
> > > again later.
> > > >Generated by squid/1.1.22 at gw.kcc.wa.edu.au
> > >
> > >
> > > Paul Baumgarten (email: paul at kcc.wa.edu.au)
> > > Information Systems Manager
> > > Kingsway Christian College
> > > 157 Kingsway, Landsdale, WA, 6065
> > > Ph: +61 8 9409 7078
> > > Fx: +61 8 9409 6179
> > >
> >
>