From: Konstantin Ryabitsev <mricon@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
StableKernel <stable@vger.kernel.org>,
LinuxKernel <linux-kernel@vger.kernel.org>
Subject: Re: Latest kernel version no NOT reflecting on kernel.org
Date: Wed, 28 Aug 2019 15:39:08 -0400 [thread overview]
Message-ID: <20190828193908.GC26001@chatter.i7.local> (raw)
In-Reply-To: <20190828170547.GA11688@kroah.com>
On Wed, Aug 28, 2019 at 07:05:47PM +0200, Greg KH wrote:
>> > I think there's a way to see which cdn mirror you are hitting when
>> > you
>> > ask for "www.kernel.org". Konstantin, any hints as to see if maybe one
>> > of the mirrors is out of sync?
>>
>> Looks like the Singapore mirror was feeling out-of-sorts. It'll start
>> feeling better shortly.
>
>Great, thanks for looking into this!
BTW, the easiest way to figure out which frontend you're hitting is to
look at the output of "host www.kernel.org", e.g.:
$ host www.kernel.org
www.kernel.org is an alias for git.kernel.org.
git.kernel.org is an alias for ord.git.kernel.org.
ord.git.kernel.org has address 147.75.58.133
ord.git.kernel.org has IPv6 address 2604:1380:4020:600::1
The three-letter airport code should indicate where the frontend is
located (in my case, ORD = Chicago). There are total of 6:
sea.git.kernel.org - Seattle
lax.git.kernel.org - Los Angeles
ord.git.kernel.org - Chicago
fra.git.kernel.org - Frankfurt
sin.git.kernel.org - Singapore
syd.git.kernel.org - Sydney
Geodns magic should send you to the nearest one, and if the monitoring
recognizes that one of them is down, it will be automatically removed
from the pool until it recovers.
Best,
-K
next prev parent reply other threads:[~2019-08-28 19:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 13:57 Latest kernel version no NOT reflecting on kernel.org Bhaskar Chowdhury
2019-08-28 15:13 ` Greg KH
2019-08-28 16:01 ` Konstantin Ryabitsev
2019-08-28 17:05 ` Greg KH
2019-08-28 19:39 ` Konstantin Ryabitsev [this message]
2019-08-28 22:52 ` Bhaskar Chowdhury
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190828193908.GC26001@chatter.i7.local \
--to=mricon@kernel.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=unixbhaskar@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.