Re: Bad mirror error during network installation
Andrew Sackville-West(andrew@farwestbilliards.com) is reported to have said:
> On Wed, Dec 06, 2006 at 01:59:17PM -0500, Wayne Topa wrote:
> > Andrew Sackville-West(andrew@farwestbilliards.com) is reported to have said:
> > > On Tue, Dec 05, 2006 at 06:56:12PM -0500, Wayne Topa wrote:
> > > >
> > > > Today the best one [1], for me, keeps dropping out while I'm
> > > > upgrading.
> > > >
> > > > [1] debian.fifi.org
> > >
> > >
> > > I use debian.midco.net and it always works great for me.
> >
> > VT1 root-3-ETCH:~# fping debian.midco.net
> > debian.midco.net is unreachable
> >
> > VT1 root-3-ETCH:~# fping http://debian.midco.net
> > http://debian.midco.net address not found
>
>
> sounds like you have bigger problems...
>
> can you ping with ip address (debian.midco.net is 24.220.0.37).
>
I can ping/update/upgrade to 2-3 mirrors anytime.
Interesting, an fping of debian.midco.net as above, unreachable, but
ping to either debian.midco.net or 24.220.0.37 does respond correctly.
ping -C 5 -q debian.midco.net gets
debian.midco.net : - - - - - which shows the response time in ms
so it's just slow to respond or busy doing your upgrades. :-)
ping -c 5 debian.midco.net shows
5 packets transmitted, 5 received, 0% packet loss, time 4015ms
rtt min/avg/max/mdev = 7347.666/7644.392/7845.698/233.619 ms, pipe 5
ping -c 5 debian.fifi.org shows
5 packets transmitted, 3 received, 40% packet loss, time 4013ms
rtt min/avg/max/mdev = 6761.549/7377.889/7721.547/436.780 ms, pipe 5
3 out of 5 returned. That's may be why I was dropping out.
Increasing the interval between pings from 25ms to 50ms on fifi shows
ping -i50 -c 5 debian.fifi.org
5 packets transmitted, 5 received, 0% packet loss, time 200047ms
rtt min/avg/max/mdev = 7724.749/8273.221/9117.814/508.782 ms
BTW gathered these results while a machine on the LAN is updating from
mirror.kernel.org, and I see it has just completed the update. :-)
I just checked my sources.list and find that, at one time, I did use
debian.midco.net. They are commented out now and, as that list must go
back 3-4 years at least, I don't recall why I switched from there.
Looks like a plain fping is not a good indicator of Up/Down. I will
use fping -C 5 -i50 in the future.
Thanks for the brain kick, Andrew, I'm forgetting more and more lately
and a good prod is always welcomed, here. After running debian for so
long, 13 years now, I sometime forget that there are so many ways to
'skin the cat' with Unix/Linux that I shouldn't stop with just one
test.
This was fun! I enjoyed the exercise, thanks!
Wayne
--
It is easier to write an incorrect program than understand a correct
one.
_______________________________________________________
Reply to: