git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git problems on Kernel.org?

From
A Large Angry SCM <gitzilla@gmail.com>
Date
Sep 11, 2005, 15:54 UTC
Message-ID
<4324531B.3080209@gmail.com>
In-Reply-To
<4323E3C0.1090109@tuxrocks.com>
Frank Sorenson wrote:
Show 23 quoted lines
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Something appears to be something odd going on with the git repos on
> kernel.org, including both the git and linux trees.  I believe that I've
> tracked down the problem to differences that occur between the repos
> located at the various IPs that kernel.org translates to (zeus-pub1:
> 204.152.191.5 and zeus-pub2: 204.152.191.37).
> 
> In this case, it appears that the repo located at zeus-pub1 has been
> updated, but the changes haven't propagated over to zeus-pub2 yet.  The
> result is that one call fetches a list of objects, but the next call
> goes to the other IP, and it can't find an object it needs, so it ends
> up dying.
> 
> This is probably a temporary error that will periodically (and probably
> very rarely) occur when pulling from a source with more than a single IP
> and some lag before the mirror is updated.
> 
> Is this an issue that we need to watch for and program around (other
> than forcing www.kernel.org's IP in /etc/hosts), or is it just one of
> those things that should be such a rare occurrance that we shouldn't
> have to worry about it?
 From a gitweb perspective, one of the servers appears to be about 24 
hours out of date as of Sun Sep 11 15:50:53 UTC 2005. Broken rsync process?
Previous: Frank SorensonNext: Nathan Laredo
Message 2 of 3 in “git problems on Kernel.org?”
  1. Frank SorensonSep 11, 2005
  2. A Large Angry SCMSep 11, 2005
  3. Nathan LaredoSep 11, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.