On Tue, Aug 30, 2011 at 07:30:01PM +0400, Oleg Broytman wrote:
PyPI went down
More information: ports 80 and 443 are open, the servers performs SSL
handshake but timeouts on HTTP requests (with or without SSL).
Oleg.
--
Oleg Broytmanhttp://phdru.name/
It is back up. I am very sorry for the fuss.
Oleg.
--
Oleg Broytmanhttp://phdru.name/p...@phdru.name
Programmers don't die, they just GOSUB without RETURN.
___
Python-Dev mailing list
Python-Dev@python.org
Hello!
I released the first package of two and PyPI went down while I was
preparing to release the second. I hope it wasn't me?
Oleg.
--
Oleg Broytmanhttp://phdru.name/p...@phdru.name
Programmers don't die, they just GOSUB without RETURN.
I released the first package of two and PyPI went down while I was
preparing to release the second. I hope it wasn't me?
A few minutes ago, it was responding very slowly, and I found out that
Postgres consumes all time. I haven't put energy into investigating what
was causing this -
On Tue, Aug 30, 2011 at 18:46, Martin v. Löwis mar...@v.loewis.de wrote:
I released the first package of two and PyPI went down while I was
preparing to release the second. I hope it wasn't me?
A few minutes ago, it was responding very slowly, and I found out that
Postgres consumes all
Looks like the issue keeps popping up. It was slow to respond earlier
today, and I keep getting complaints about it (including now.)
Somebody is mirroring the site with wget. I have null-routed them.
Regards,
Martin
___
Python-Dev mailing list
