[prev in list] [next in list] [prev in thread] [next in thread] 

List:       python-catalog-sig
Subject:    Re: [Catalog-sig] [Pydotorg]  PyPI down
From:       "Martin_v._Löwis" <martin () v ! loewis ! de>
Date:       2007-08-01 21:09:53
Message-ID: 46B0F6A1.7010600 () v ! loewis ! de
[Download RAW message or body]

> Perhaps the CPU load was so high that the PyPI FCGI took a long time
> to open its socket, such a long time that Apache concluded that it
> hadn't started.  

I think in this case, mod_fcgi would log a message "failed to respond"
or some such. The actual log message was like "pypi.fcgi exited with
status code 0" - so it wasn't killed (IIUC). I added syslog messages
to pypi.fcgi; it looks like something raises SystemExit, so pypi.fcgi
terminates "voluntarily". I'm not quite sure where the exit comes
from (but I since added logs to the two SystemExit occurrences in
thfcgi.py).

What is puzzling is that it will immediately do the same thing after
being started fresh.

Regards,
Martin
_______________________________________________
Catalog-SIG mailing list
Catalog-SIG@python.org
http://mail.python.org/mailman/listinfo/catalog-sig
[prev in list] [next in list] [prev in thread] [next in thread]