LFS-Museum // archive.linuxfromscratch.org down?
lfs65 at cruziero.com
Tue Jul 2 13:19:57 PDT 2013
> From bruce.dubbs at gmail.com Tue Jul 2 19:06:53 2013
> Date: Tue, 02 Jul 2013 12:54:45 -0500
> Subject: Re: LFS-Museum // archive.linuxfromscratch.org down?
> akhiezer wrote:
> >> From bruce.dubbs at gmail.com Tue Jul 2 16:41:49 2013
> >> Date: Tue, 02 Jul 2013 10:29:42 -0500
> >> To: akhiezer <lfs65 at cruziero.com>,
> >> Website Maintenance List <website at linuxfromscratch.org>
> >> Subject: Re: LFS-Museum // archive.linuxfromscratch.org down?
> >> akhiezer wrote:
> >>> Hi,
> >>> Looks like LFS-Museum // archive.linuxfromscratch.org is down or at
> >>> least not resolving, since ca yesterday ?
> >>> Could access to it be made available again, please?
> > .
> > .
> >> http://archive.linuxfromscratch.org/ seems to work for me.
> >> $ dig archive.linuxfromscratch.org
> > .
> > .
> >> ;; ANSWER SECTION:
> >> archive.linuxfromscratch.org. 638 IN CNAME
> >> archives.linuxfromscratch.org.
> >> archives.linuxfromscratch.org. 638 IN CNAME higgs.linuxfromscratch.org.
> >> higgs.linuxfromscratch.org. 638 IN A 220.127.116.11
> > .
> > .
> > It's been intermittent today, since a short while after my first email today.
> > When it resolves, it shows the info that you posted, above (ie the
> > higgs/archives/18.104.22.168/etc). If I use the IP-address, or use the
> > hostname 'archive.linuxfromscratch.org' and cached local dns info, then when try
> > to access a few small downloads via wget or browser, very often get 'connection
> > refused' errors back: is there some sort of throttling going on?
> Not that I know about.
And yet for example if I let wget use its default 'user-agent' value, it's quite
easy to hit 'connection refused' messages: and a second or so later I issue the
same command but with the 'user-agent' value either spoofed to a common browser
string, or set to empty string, and get through OK: and a second or so later if
I use same command line but with 'user-agent' value again as wget default, then
it's quite easy to hit 'connection refused' again.
> > And if I bypass
> > dns-cache and use 'archive.linuxfromscratch.org' then is OK sometimes, but very
> > often get 'cannot resolve' errors.
> Add to /etc/hosts
> 22.214.171.124 archives.linuxfromscratch.org
> You may also want to edit /etc/resolv.conf
> domain linuxfromscratch.org
> nameserver 126.96.36.199
> nameserver 188.8.131.52
> The nameservers are Google.
This kindof ignores the following point that it's observed at various
locations/ISPs/etc, at various times over the ast 6 months or so.
> > I've seen this kind of pattern several times since approx start of the year; and
> > from various locations/ISPs/etc. Hadn't mentioned it til now as thought it may be
> > just the new setup settling down.
> > More widely: do any of the mirrors carry that 'museum' stuff? I couldn't see it
> > in them. Or does the museum stuff not get mirrored? If the latter, then is it
> > possible to have it such that it gets included in the mirrors?
Is it possible to have the 'museum' stuff included in the mirrors? The likes of
'http://www.linuxfromscratch.org/lfs/view/' does get mirrored (ref e.g.
'http://ftp.osuosl.org/pub/lfs/lfs-packages/'), and it contains 6.1.1 onwards.
Why not just go right back to the earliest versions? Some might say that anything
as 'old' as, say, 6.5 should be in museum (some would say anything older than
last week). Wouldn't it be better just to have everything all in the one place,
or at least every version mirrored?
> I've seen no access problem at all. How many hops does traceroute show
> for you? I get:
> traceroute to 184.108.40.206 (220.127.116.11), 64 hops max
> 1 * * *
> 2 18.104.22.168 (22.214.171.124) 12.455ms 7.648ms 8.068ms
> 3 126.96.36.199 (188.8.131.52) 11.207ms 8.003ms 8.079ms
> 4 184.108.40.206 (220.127.116.11) 11.871ms 7.904ms 8.977ms
> 5 18.104.22.168 (22.214.171.124) 15.672ms 15.988ms 15.921ms
> 6 126.96.36.199 (188.8.131.52) 14.654ms 11.935ms 11.953ms
> 7 184.108.40.206 (220.127.116.11) 17.664ms 19.977ms 19.915ms
> 8 18.104.22.168 (22.214.171.124) 16.156ms 15.947ms 15.972ms
> 9 126.96.36.199 (188.8.131.52) 32.691ms 65.672ms 23.074ms
> 10 184.108.40.206 (220.127.116.11) 56.372ms 55.426ms 56.458ms
> 11 18.104.22.168 (22.214.171.124) 65.802ms 53.917ms 53.928ms
> 12 126.96.36.199 (188.8.131.52) 64.944ms 63.133ms 72.098ms
> 13 184.108.40.206 (220.127.116.11) 68.970ms 75.055ms 74.869ms
> 14 18.104.22.168 (22.214.171.124) 65.560ms 64.081ms 65.836ms
> 15 126.96.36.199 (188.8.131.52) 63.935ms 64.568ms 67.019ms
traceroute to 184.108.40.206 (220.127.116.11), 30 hops max, 60 byte packets
1 18.104.22.168 0.185 ms 0.139 ms 0.105 ms
2 22.214.171.124 20.156 ms 20.111 ms 20.083 ms
3 126.96.36.199 28.042 ms 28.012 ms 27.974 ms
4 188.8.131.52 19.930 ms 19.901 ms 19.872 ms
5 184.108.40.206 29.538 ms 29.517 ms 29.489 ms
6 220.127.116.11 27.626 ms 27.447 ms 27.414 ms
7 18.104.22.168 105.305 ms 101.666 ms 101.574 ms
8 22.214.171.124 190.588 ms 190.513 ms 126.96.36.199 190.531 ms
9 188.8.131.52 168.393 ms 163.380 ms 163.354 ms
10 184.108.40.206 165.498 ms 165.443 ms 165.412 ms
11 220.127.116.11 164.148 ms 164.698 ms 164.668 ms
More information about the website