[pydotorg-www] gnutls_handshake() failed: Error in the pull function
Hello, For some time now, I have had sporadic failures when browsing to www.python.org and related websites such as docs.python.org. With Firefox, I would simply get a blank page without any error message whatsoever. With curl, it manifests with the following error: $ curl -v -I https://www.python.org/ * Trying 2a04:4e42:a::223... * Trying 151.101.40.223... * Connected to www.python.org (2a04:4e42:a::223) port 443 (#0) * found 173 certificates in /etc/ssl/certs/ca-certificates.crt * found 704 certificates in /etc/ssl/certs * ALPN, offering http/1.1 * gnutls_handshake() failed: Error in the pull function. * Closing connection 0 curl: (35) gnutls_handshake() failed: Error in the pull function. It is extremely irregular, sometimes it doesn't happen, sometimes several times in a row, sometimes once in a while. Is anyone else noticing this? Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org https://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Poll about -h,--help options
On Mon, 18 Feb 2013 10:40:07 +0300 anatoly techtonik wrote: > Hi, > > Is it interesting to know if people expect -h to work as a --help > equivalent by default? Yes, I do expect it. (and I find it quite annoying when it doesn't) Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] [Infrastructure] Migrating python.org to OSL
Le mardi 19 mars 2013 à 08:44 +0100, M.-A. Lemburg a écrit :
> On 19.03.2013 00:27, Noah Kantrowitz wrote:
> >
> > On Mar 18, 2013, at 4:23 PM, M.-A. Lemburg wrote:
> >
> >> Noah Kantrowitz wrote:
> >>> As part of the PyCon sprints I would like to move python.org off dinsdale
> >>> to a VM at OSL. Due to the build system being tied to SVN, I'll also
> >>> migrate that service on the same VM. Do any SVN repos other than www/
> >>> need to remain available? This would require at least some period of not
> >>> changing the website, probably a few hours, but I don't think that would
> >>> be a problem. This is mostly a legacy move so I'm not going to clean it
> >>> up much, we'll have a new site soon enough.
> >>
> >> The repos with public interfaces:
> >>
> >> http://svn.python.org/view/
> >>
> >> will need to remain available to keep old links in e.g.
> >> bug reports working.
> >
> > Okay, thats just a single repo ("projects") which is the default one. The
> > packages repo is also visible but I'm okay with breaking that given how
> > most code has been removed in the current trunk and links are rare (thats
> > the old home for the PyPI code and related stuffs). Are we okay with that
> > projects repo being full read-only?
>
> Looking at the page, there are some checkins which are only
> a few months old, so I'm not sure whether those can be
> made read-only, e.g. external/ or sandbox/
external/ holds snapshots of 3rd-party libs (OpenSSL, etc.) that are
used for e.g. Windows builds and doc builds.
OTOH, "old links in bug reports" don't need SVN to work, they are mapped
onto a conversion Web service in hg.python.org: e.g.
http://hg.python.org/lookup/r12345
Regards
Antoine.
___
pydotorg-www mailing list
pydotorg-www@python.org
http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] PyPI HTTPS access fails with IPv4
v.loewis.de> writes: > > Zitat von Antoine Pitrou : > > I am noticing a weird stylesheet difference between HTTP PyPI and HTTPS > > PyPI, > > and it boils down to HTTPS access failing with IPv4: > > The bug is really in PyPI. www.python.org does not support https, so > PyPI should > really copy the CSS files locally. Ah, true. For some reason, connecting works with IPv6 but then handles the request to the SVN virtual host: $ LANG=C curl -vk https://www.python.org/styles/screen-switcher-default.css * About to connect() to www.python.org port 443 (#0) * Trying 2001:888:2000:d::a2... connected * Connected to www.python.org (2001:888:2000:d::a2) port 443 (#0) [ ... ] > GET /styles/screen-switcher-default.css HTTP/1.1 > User-Agent: curl/7.21.0 (i486-pc-linux-gnu) libcurl/7.21.0 OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.15 libssh2/1.2.6 > Host: www.python.org > Accept: */* > < HTTP/1.1 401 Authorization Required < Date: Sun, 23 Sep 2012 18:13:48 GMT < Server: Apache/2.2.16 (Debian) < WWW-Authenticate: Basic realm="Subversion repository" < Content-Length: 482 < Content-Type: text/html; charset=iso-8859-1 [ etc. ] Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
[pydotorg-www] PyPI HTTPS access fails with IPv4
Hello, I am noticing a weird stylesheet difference between HTTP PyPI and HTTPS PyPI, and it boils down to HTTPS access failing with IPv4: $ LANG=C curl -v http://www.python.org/styles/screen-switcher-default.css * About to connect() to www.python.org port 80 (#0) * Trying 82.94.164.162... connected * Connected to www.python.org (82.94.164.162) port 80 (#0) [ snip successful reply ] $ LANG=C curl -v https://www.python.org/styles/screen-switcher-default.css * About to connect() to www.python.org port 443 (#0) * Trying 82.94.164.162... Connection refused * Trying 2001:888:2000:d::a2... Failed to connect to 2001:888:2000:d::a2: Network is unreachable * Success * couldn't connect to host * Closing connection #0 curl: (7) Failed to connect to 2001:888:2000:d::a2: Network is unreachable Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
[pydotorg-www] HTTPS pypi site malfunctioning?
Hello, When browing on https://pypi.python.org/pypi, the CSS doesn't seem activated. (it is on http://pypi.python.org/pypi) Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] [python-committers] Deleting code.python.org
Le lundi 02 juillet 2012 à 17:57 +0200, mar...@v.loewis.de a écrit : > code.python.org was meant as a VCS-independent hostname for CPython; > PEP 385 chose to use hg.python.org instead. > > I'd like to delete code.python.org. Objections? Sounds fine to me. cheers Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] [Python-Dev] [Infrastructure] Buildbot master moved
On Thu, 28 Jun 2012 19:08:44 +0200 Hynek Schlawack wrote: > > Now someone needs to incorporate these changes into our local git. I'm a > > git newbie, and basic commands seem to fail for me: > > > > $ git fetch -v > > Permission denied (publickey). > > fatal: The remote end hung up unexpectedly > > > > Hynek, do you want to help? > > I'd love to, but I'm afk for the rest of the (CEST) day. :( If it's broken > still broken tomorrow, you know where to find me. :) Ok, I've applied the patches by hand in the local repo, without committing them. It seems to fix the issue AFAICT. Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] [Infrastructure] [Python-Dev] Buildbot master moved
Le jeudi 28 juin 2012 à 18:09 +0200, Antoine Pitrou a écrit : > Le jeudi 28 juin 2012 à 16:04 +0200, Hynek Schlawack a écrit : > > Hi, > > > > I don’t know if it’s known, but the bot infrastructure is FUBAR now. > > http://buildbot.python.org/all/waterfall is a stacktrace and all tests > > fail because of the XML-RPC tests that use our buildbot API. > > It works if you reload the page, though. Looks like a weird bug in > buildbot, has anyone reported it upstream? Ok, apparently it's http://trac.buildbot.net/ticket/2301 and it seems to have been fixed upstream. Now someone needs to incorporate these changes into our local git. I'm a git newbie, and basic commands seem to fail for me: $ git fetch -v Permission denied (publickey). fatal: The remote end hung up unexpectedly Hynek, do you want to help? Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] [Python-Dev] [Infrastructure] Buildbot master moved
Le jeudi 28 juin 2012 à 16:04 +0200, Hynek Schlawack a écrit : > Hi, > > I don’t know if it’s known, but the bot infrastructure is FUBAR now. > http://buildbot.python.org/all/waterfall is a stacktrace and all tests > fail because of the XML-RPC tests that use our buildbot API. It works if you reload the page, though. Looks like a weird bug in buildbot, has anyone reported it upstream? Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] [Infrastructure] Buildbot master moved
Le jeudi 28 juin 2012 à 12:11 +0200, Antoine Pitrou a écrit : > Le jeudi 28 juin 2012 à 12:06 +0200, Antoine Pitrou a écrit : > > Le jeudi 28 juin 2012 à 09:13 +0200, "Martin v. Löwis" a écrit : > > > I have now moved the buildbot master to OSU/OSL, and upgraded the > > > buildbot version in the process. If there are any issues, let me > > > know or Antoine. > > > > It seems we lost the "force build" button. Judging from the templates, > > the form is here, it just isn't displayed. > > > > I also don't see any custom builders: > > http://buildbot.python.org/all/waterfall?category=custom.stable&category=custom.unstable Ok, both are fixed. Note: there are uncommitted changes in the local git repo, I left them uncommitted. Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] [Infrastructure] Buildbot master moved
Le jeudi 28 juin 2012 à 12:06 +0200, Antoine Pitrou a écrit : > Le jeudi 28 juin 2012 à 09:13 +0200, "Martin v. Löwis" a écrit : > > I have now moved the buildbot master to OSU/OSL, and upgraded the > > buildbot version in the process. If there are any issues, let me > > know or Antoine. > > It seems we lost the "force build" button. Judging from the templates, > the form is here, it just isn't displayed. > > I also don't see any custom builders: > http://buildbot.python.org/all/waterfall?category=custom.stable&category=custom.unstable Ok, it seems we should migrate to the ForceScheduler API: http://buildbot.net/buildbot/docs/0.8.6/manual/cfg-schedulers.html#forcescheduler-scheduler ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] [Infrastructure] Buildbot master moved
Le jeudi 28 juin 2012 à 09:13 +0200, "Martin v. Löwis" a écrit : > I have now moved the buildbot master to OSU/OSL, and upgraded the > buildbot version in the process. If there are any issues, let me > know or Antoine. It seems we lost the "force build" button. Judging from the templates, the form is here, it just isn't displayed. I also don't see any custom builders: http://buildbot.python.org/all/waterfall?category=custom.stable&category=custom.unstable Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] [Infrastructure] python.org down?
> > I've rebooted the machine, it was stuck again. So far I couldn't see > > anything > > interesting in the log files. > > What's being done to diagnose this further? http://mail.python.org/pipermail/pydotorg-www/2012-January/001572.html > 2 outages in the space of 3 or 4 days doesn't look to good. We already had repeated outages 6 months ago, it had calmed down afterwards. > How does this correlate with pypi being moved to dinsdale? Don't know. Perhaps higher system load increases the likelihood of outages. Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] dinsdale rebooted
M.-A. Lemburg writes: > Looks like the /dev/sda disk is broken. Could you run smartctl > on the drive and check that smartd is running on dinsdale (and sending > emails to this list or pydotorg) ? It's an Adaptec RAID controller. Someone should perhaps check whether one of the drives in the RAID array needs replacement. Also, it seems there may be issues with some Adaptec firmware versions: https://forums.openfiler.com/viewtopic.php?id=2162 Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
[pydotorg-www] dinsdale rebooted
Hello, dinsdale was unresponsive (all the services) so I've rebooted it. The services should go back online after the boot sequence is finished. (hopefully I didn't mess with anything when doing that) Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Repeated outages of python.org
M.-A. Lemburg writes: > > If you look through the archives, it's very easy to find out about > the infrastructure setup being used to run python.org. Take e.g. > this thread as example: > > http://markmail.org/thread/kcxkjbesmbweaaj6#query:+page:1+mid:kcxkjbesmbweaaj6+state:results I'm not sure what is sensitive in that thread. Any determined attacker can certainly get that information (and much more) by themselves. All in all, I agree with Michael. It is important that people can know easily if a problem has been reported or not, without having to subscribe or log in. It is also important to know if problems are being acted upon, again without having to subscribe. Obviously, sensitive information should only be communicated privately, but that shouldn't rule out the existence of a public channel. Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Repeated outages of python.org
It doesn't look like a software problem at all, perhaps xs4all could take a look at the hardware and see if something seems problematic? Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Repeated outages of python.org
Georg Brandl writes: > > Do we have the resources to monitor it a little more carefully > from now on until we found out what the cause is? Could it be > some kind of attack? It looks like power-cycling privileges should be given to more people (Georg for example :-)), to avoid potentially long outages likes this. Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
[pydotorg-www] Issues on dinsdale?
Hello, So, dinsdale seems to have become very slow again. I can't login by ssh on it: $ ssh dinsdale.python.org ssh: connect to host dinsdale.python.org port 22: Network is unreachable Here is a traceroute from a well-connected machine: # traceroute dinsdale.python.org traceroute to dinsdale.python.org (82.94.164.162), 30 hops max, 60 byte packets 1 vl2001-swr601-vmr-stdenis.vmr.nerim.net (195.5.228.255) 0.640 ms 1.036 ms 1.214 ms 2 gi1-12-800-nb-stdenis-2.nerim.net (194.79.128.242) 0.940 ms 1.028 ms 1.116 ms 3 te2-2-94-nb-voltaire-1.nerim.net (194.79.131.89) 1.229 ms 1.227 ms 1.330 ms 4 gi0-1-giaco.nerim.net (194.79.131.78) 9.802 ms 9.801 ms 9.829 ms 5 ams-ix.tc2.xs4all.net (195.69.144.166) 10.393 ms 115.720 ms 116.014 ms 6 0.so-2-0-0.xr4.1d12.xs4all.net (194.109.5.9) 10.368 ms 10.150 ms 10.690 ms 7 te5-4.swcolo2.3d12.xs4all.net (194.109.12.34) 11.195 ms 10.703 ms 11.181 ms 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * # tcptraceroute dinsdale.python.org 80 traceroute to dinsdale.python.org (82.94.164.162), 30 hops max, 60 byte packets 1 vl2001-swr601-vmr-stdenis.vmr.nerim.net (195.5.228.255) 0.657 ms 1.066 ms 1.236 ms 2 gi1-12-800-nb-stdenis-2.nerim.net (194.79.128.242) 0.611 ms 0.823 ms 0.815 ms 3 te2-2-94-nb-voltaire-1.nerim.net (194.79.131.89) 0.977 ms 1.040 ms 1.206 ms 4 gi0-1-giaco.nerim.net (194.79.131.78) 9.696 ms 9.689 ms 9.681 ms 5 ams-ix.tc2.xs4all.net (195.69.144.166) 10.456 ms 10.436 ms 10.438 ms 6 0.so-2-0-0.xr4.1d12.xs4all.net (194.109.5.9) 10.397 ms 10.245 ms 10.193 ms 7 te5-4.swcolo2.3d12.xs4all.net (194.109.12.34) 10.365 ms 10.494 ms 10.385 ms 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Connectivity/network problems?
On Tue, 01 Feb 2011 20:54:31 +0100 "Martin v. Löwis" wrote: > > Actually, I've just managed to reproduce it from dinsdale itself: > > So I doubt that it's an issue with the networking configuration; > more likely, this looks like a Mercurial bug. Well, at this point it could be an issue anywhere on the host machine, including Mercurial, mod_wsgi, Apache, or the kernel network stack. I've tried to reproduce with Wireshark capturing, but still haven't managed to. Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Connectivity/network problems?
On Tue, 01 Feb 2011 01:31:39 +0100
"Martin v. Löwis" wrote:
> >>> 213.41.240.54 - - [30/Jan/2011:17:05:45 +0100] "GET
> >>> /hg/branches/release2.7-maint/?cmd=changegroup&roots=
> >>> HTTP/1.1" 200 5149626 "-" "mercurial/proto-1.0"
> >>>
> >>> (this is not UTC, but DLT - Dinsdale Local Time ;-))
> >>
> >> So what was the problem? Looks like a successful request to me.
> >
> > No, the transfer size should have been much larger. The hg clone ended
> > up corrupted. A later attempt got the correct full transfer:
> >
> > 213.41.240.54 - - [30/Jan/2011:17:10:15 +0100]
> > "GET
> > /hg/branches/release2.7-maint/?cmd=changegroup&roots=
> > HTTP/1.1" 200 77229968 "-" "mercurial/proto-1.0"
>
> Ah. Could this be a request timeout? How long does the cloning take?
> There is a global apache timeout of 300s; not sure whether that's
> relevant.
I don't think so. The cloning just failed again, much quicker:
$ time hg clone http://code.python.org/hg/branches/release2.7-maint/
destination directory: release2.7-maint
requesting all changes
adding changesets
adding manifests
adding file changes
transaction abort!
rollback completed
abandon : premature EOF reading chunk (got 2517 bytes, expected 5105)
Command exited with non-zero status 255
19.66user 1.01system 0:46.80elapsed 44%CPU (0avgtext+0avgdata
203504maxresident)k 3648inputs+79040outputs
$ LANG=C date
Tue Feb 1 14:38:42 CET 2011
Actually, I've just managed to reproduce it from dinsdale itself:
$ time hg clone http://code.python.org/hg/branches/release2.7-maint/
destination directory: release2.7-maint
requesting all changes
adding changesets
adding manifests
adding file changes
transaction abort!
rollback completed
** unknown exception encountered, please report by visiting
** http://mercurial.selenic.com/wiki/BugTracker
** Python 2.5.2 (r252:60911, Jan 24 2010, 14:53:14) [GCC 4.3.2]
** Mercurial Distributed SCM (version 1.7.3)
** Extensions loaded:
Traceback (most recent call last):
File "/usr/bin/hg", line 38, in
mercurial.dispatch.run()
File "/var/lib/python-support/python2.5/mercurial/dispatch.py", line 16, in
run
sys.exit(dispatch(sys.argv[1:]))
File "/var/lib/python-support/python2.5/mercurial/dispatch.py", line 36, in
dispatch
return _runcatch(u, args)
File "/var/lib/python-support/python2.5/mercurial/dispatch.py", line 58, in
_runcatch
return _dispatch(ui, args)
File "/var/lib/python-support/python2.5/mercurial/dispatch.py", line 590, in
_dispatch
cmdpats, cmdoptions)
File "/var/lib/python-support/python2.5/mercurial/dispatch.py", line 401, in
runcommand
ret = _runcommand(ui, options, cmd, d)
File "/var/lib/python-support/python2.5/mercurial/dispatch.py", line 641, in
_runcommand
return checkargs()
File "/var/lib/python-support/python2.5/mercurial/dispatch.py", line 595, in
checkargs
return cmdfunc()
File "/var/lib/python-support/python2.5/mercurial/dispatch.py", line 588, in
d = lambda: util.checksignature(func)(ui, *args, **cmdoptions)
File "/var/lib/python-support/python2.5/mercurial/util.py", line 426, in check
return func(*args, **kwargs)
File "/var/lib/python-support/python2.5/mercurial/commands.py", line 736, in
clone
branch=opts.get('branch'))
File "/var/lib/python-support/python2.5/mercurial/hg.py", line 337, in clone
dest_repo.clone(src_repo, heads=revs, stream=stream)
File "/var/lib/python-support/python2.5/mercurial/localrepo.py", line 1886,
in clone
return self.pull(remote, heads)
File "/var/lib/python-support/python2.5/mercurial/localrepo.py", line 1295,
in pull
return self.addchangegroup(cg, 'pull', remote.url(), lock=lock)
File "/var/lib/python-support/python2.5/mercurial/localrepo.py", line 1739,
in addchangegroup
if fl.addgroup(source, revmap, trp) is None:
File "/var/lib/python-support/python2.5/mercurial/revlog.py", line 1381, in
addgroup
p1, p2, (chainrev, delta), ifh, dfh)
File "/var/lib/python-support/python2.5/mercurial/revlog.py", line 1220, in
_addrevision
cachedelta[1])
mpatch.mpatchError: patch cannot be decoded
real1m15.848s
user0m52.479s
sys 0m2.120s
svn2hg@dinsdale:~/t$ LANG=C date
Tue Feb 1 14:45:10 CET 2011
Cloning locally (without network access) succeeds:
$ time hg clone --pull /data/home/svn2hg/cpython/public_27-full/
destination directory: public_27-full
requesting all changes
adding changesets
adding manifests
adding file changes
added 45831 changesets with 99150 changes to 8586 files
updating to branch release27-maint
4218 files updated, 0 files merged, 0 files removed, 0 files unresolved
real1m31.074s
user1m26.053s
sys 0m3.260s
Regards
Antoine.
___
pydotorg-www mailing list
pydotorg-www@python.org
http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Connectivity/network problems?
On Tue, 01 Feb 2011 00:55:19 +0100 "Martin v. Löwis" wrote: > Am 01.02.2011 00:29, schrieb Antoine Pitrou: > > On Tue, 01 Feb 2011 00:17:04 +0100 > > "Martin v. Löwis" wrote: > >> If you can reproduce the problem, please take note and report the > >> exact date and time of the problem (in UTC). > > > > One such occurrence could be: > > > > 213.41.240.54 - - [30/Jan/2011:17:05:45 +0100] "GET > > /hg/branches/release2.7-maint/?cmd=changegroup&roots= > > HTTP/1.1" 200 5149626 "-" "mercurial/proto-1.0" > > > > (this is not UTC, but DLT - Dinsdale Local Time ;-)) > > So what was the problem? Looks like a successful request to me. No, the transfer size should have been much larger. The hg clone ended up corrupted. A later attempt got the correct full transfer: 213.41.240.54 - - [30/Jan/2011:17:10:15 +0100] "GET /hg/branches/release2.7-maint/?cmd=changegroup&roots= HTTP/1.1" 200 77229968 "-" "mercurial/proto-1.0" ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Connectivity/network problems?
On Tue, 01 Feb 2011 00:17:04 +0100 "Martin v. Löwis" wrote: > If you can reproduce the problem, please take note and report the > exact date and time of the problem (in UTC). One such occurrence could be: 213.41.240.54 - - [30/Jan/2011:17:05:45 +0100] "GET /hg/branches/release2.7-maint/?cmd=changegroup&roots= HTTP/1.1" 200 5149626 "-" "mercurial/proto-1.0" (this is not UTC, but DLT - Dinsdale Local Time ;-)) Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] Connectivity/network problems?
Antoine Pitrou writes: > > > Even a normal static HTTP request can fail on the TCP layer (this is > sporadic): By the way a traceroute launched at the same moment seems to indicate that c.p.o doesn't always answer: $ sudo tcptraceroute code.python.org 80 traceroute to code.python.org (82.94.164.162), 30 hops max, 40 byte packets 1 vl2001-swr601-vmr-stdenis.vmr.nerim.net (195.5.228.255) 0.625 ms 1.018 ms 1.193 ms 2 gi1-11-800-nb-stdenis-1.nerim.net (194.79.128.241) 0.661 ms 0.740 ms 0.822 ms 3 te2-4-80-nb-stdenis-2.nerim.net (194.79.128.66) 100.745 ms 100.807 ms 101.031 ms 4 te2-2-94-nb-voltaire-1.nerim.net (194.79.131.89) 0.901 ms 1.230 ms 1.226 ms 5 gi0-1-giaco.nerim.net (194.79.131.78) 9.532 ms 9.571 ms 9.557 ms 6 ams-ix.tc2.xs4all.net (195.69.144.166) 10.170 ms 10.815 ms 9.893 ms 7 0.so-2-0-0.xr4.1d12.xs4all.net (194.109.5.9) 10.784 ms 10.333 ms 10.433 ms 8 te5-4.swcolo2.3d12.xs4all.net (194.109.12.34) 10.295 ms 9.978 ms 10.199 ms 9 dinsdale.python.org (82.94.164.162) 11.411 ms 10.088 ms * Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
[pydotorg-www] Connectivity/network problems?
Hello, It seems code.python.org (perhaps other hosts) sometimes has slight network problems. Users have been reporting problems coding the hg mirrors recently, see the latest messages on http://mercurial.selenic.com/bts/issue2595 (the machine itself looks fine, lots of free RAM and disk, idle CPUs; also the Apache logs don't seem to show any mod_wsgi crashes or issues) Even a normal static HTTP request can fail on the TCP layer (this is sporadic): $ curl -v http://code.python.org/robots.txt * About to connect() to code.python.org port 80 (#0) * Trying 82.94.164.162... Timeout * Trying 2001:888:2000:d::a2... Failed to connect to 2001:888:2000:d::a2: Le réseau n'est pas accessible. * Succès * couldn't connect to host * Closing connection #0 curl: (7) Failed to connect to 2001:888:2000:d::a2: Le réseau n'est pas accessible. (This is from a well-connected machine inside a datacenter. The IPv6 error message means "network not reachable" but what's important is that the IPv4 attempt fails with a timeout) Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
Re: [pydotorg-www] bugs.python.org down
Martin v. Löwis v.loewis.de> writes: > > Am 10.11.2010 06:28, schrieb Aahz: > > Tried to connect to bugs.python.org from two different machines, no joy. > > Can anybody reproduce this? works fine for me. bugs.python.org is unavailable here, even pinging doesn't work. traceroute seems to stop somewhere in Germany: traceroute to bugs.python.org (88.198.142.26), 30 hops max, 60 byte packets 1 192.168.0.1 (192.168.0.1) 1.771 ms 2.179 ms 2.619 ms 2 lo5-nas501-dsl-courbevoie.nerim.net (194.79.136.15) 30.261 ms 32.350 ms 32.860 ms 3 vl601-na-courbevoie-1.nerim.net (194.79.136.33) 33.646 ms 34.293 ms 35.484 ms 4 te2-3-73-nb-courbevoie-1.nerim.net (194.79.136.17) 36.802 ms 38.153 ms 38.687 ms 5 te2-1-91-nb-voltaire-2.nerim.net (194.79.131.142) 40.333 ms 40.690 ms 41.501 ms 6 gi0-2-giaco.nerim.net (194.79.131.82) 51.302 ms 38.320 ms 37.923 ms 7 amsix.tng.de (195.69.145.119) 39.191 ms 40.639 ms 41.029 ms 8 amsix-gw.hetzner.de (83.141.1.59) 49.211 ms 49.663 ms 51.043 ms 9 hos-bb1.juniper1.fs.hetzner.de (213.239.240.242) 55.623 ms 56.742 ms 57.439 ms 10 hos-tr2.ex3k3.rz13.hetzner.de (213.239.224.36) 59.456 ms 60.129 ms hos-tr1.ex3k3.rz13.hetzner.de (213.239.224.4) 60.947 ms 11 * * * Regards Antoine. ___ pydotorg-www mailing list pydotorg-www@python.org http://mail.python.org/mailman/listinfo/pydotorg-www
