From: Frank Sorenson <frank@tuxrocks.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: git problems on Kernel.org?
Date: Sun, 11 Sep 2005 01:58:56 -0600 [thread overview]
Message-ID: <4323E3C0.1090109@tuxrocks.com> (raw)
-----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?
Thanks,
Frank
- --
Frank Sorenson - KD7TZK
Systems Manager, Computer Science Department
Brigham Young University
frank@tuxrocks.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDI+PAaI0dwg4A47wRAgEhAKDPjvyHZwTSw/e+FwE5BXtpH2novACdGBaF
+R64XoAYx+WXGjbczO+ZQtY=
=vCRj
-----END PGP SIGNATURE-----
next reply other threads:[~2005-09-11 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 7:58 Frank Sorenson [this message]
2005-09-11 15:54 ` git problems on Kernel.org? A Large Angry SCM
2005-09-11 18:26 ` Nathan Laredo
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=4323E3C0.1090109@tuxrocks.com \
--to=frank@tuxrocks.com \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).