PyPI down :(

Error...

There's been a problem with your request

psycopg.OperationalError: server closed the connection
unexpectedly
	This probably means the server terminated abnormally
	before or while processing the request

While trying to open http://pypi.python.org/
(15:43 UTC)
_______________________________________________
Catalog-SIG mailing list
Catalog-SIGpython.org
h
ttp://mail.python.org/mailman/listinfo/catalog-sig

On Fri, Jan 18, 2008 at 01:47:27PM -0200, Daniel (ajax)
Diniz wrote:
> There's been a problem with your request

Thanks for your report.  I've restarted the web server and
that 
seemed to clear the problem.

--amk
_______________________________________________
Catalog-SIG mailing list
Catalog-SIGpython.org
h
ttp://mail.python.org/mailman/listinfo/catalog-sig

> On Fri, Jan 18, 2008 at 01:47:27PM -0200, Daniel (ajax)
Diniz wrote:
>> There's been a problem with your request
> 
> Thanks for your report.  I've restarted the web server
and that 
> seemed to clear the problem.

I've studied this a bit. Apparently, at 9:52 UTC, the OOM
killer killed
a process (apache2), then over the next minutes it killed
more processes
(apache2, moin.fcgi, pypi.fcgi, and eventually, at 10:04, it
killed
"postmaster". That apparently resolved the
out-of-memory situation, but
it also meant that PyPI broke. The postgres log file has all
kinds of
messages on stopped and crashed servers, rolled-back
transactions etc,
but eventually, postgres recovered. Not so PyPI, which (for
some reason)
failed to reconnect to the server. Looking at the
tracebacks, it seems
that psycopg now reports OperationalError for broken
connections, and
not (anymore?) InterfaceError.

Regards,
Martin
_______________________________________________
Catalog-SIG mailing list
Catalog-SIGpython.org
h
ttp://mail.python.org/mailman/listinfo/catalog-sig