If bootstrap.pypa.io sits behind fastly, a 503 would indicate that it couldn't reach the server. That means that it is either exactly what Nick pointed out or a semi-normal error from fastly. There's a reason pip retries package downloads when it sees a 503 response status code. On Mar 3, 2015 5:30 AM, "Nick Coghlan" <[email protected]> wrote:
> On 3 March 2015 at 19:30, Reinout van Rees <[email protected]> wrote: > > Hi, > > > > I'm getting a "503 service unavailable" on https://bootstrap.pypa.io/ > > > > This effectively kills all "bootstrap.py" scripts of our buildouts :-( > > > > > > Where is the best place to report this, normally? I looked at the pypi > > bug tracker but didn't see a mention of pypa.io there. > > We don't currently have a great ticket tracking system for the PSF > infrastructure - we should probably work out something better, so > folks don't have to play "guess the project", and also so operational > issues can be more clearly separated from the development projects > that power the online services. > > Emailing [email protected] is a decent last resort option, > though, including for the PyPA parts. > > In this case, it looks like it's back now, so it may have just been > affected by the Rackspace rolling restarts earlier > (https://status.python.org/incidents/5w523lrn3587) > > Regards, > Nick. > > -- > Nick Coghlan | [email protected] | Brisbane, Australia > _______________________________________________ > Distutils-SIG maillist - [email protected] > https://mail.python.org/mailman/listinfo/distutils-sig >
_______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
