Here's a way to find out... as long as you're running FileStorage, you can run this script against your Data.fs via "list_transactions.py /your/path/Data.fs" (even if the Data.fs is open). Then you can compare the output of the script against the stupid log file to see if there were any writes to the ZODB at the time of the conflict. Other folks have complained about this and we're trying to isolate the problem... if you have time, it'd be great to hear you report back "yes, there was a write, and here was its method name", or "no, there was no write at that time, somethings messed up". - C ----- Original Message ----- From: "Dieter Maurer" <dieter@handshake.de> To: <zope@zope.org> Sent: Thursday, April 12, 2001 5:01 PM Subject: [Zope] Dangerous "cvs update"
My yesterday "cvs update" let my Zope fail to start: Panic - startup exception; type error in "ZServer/HTTPServer".
I analysed the problem:
Apparently "asyncore.py" has been moved. "cvs update" had correctly remove the Python source but (of course) left alone the corresponding "*.pyc" file.
Somehow, this old "*.pyc" file caused the problem. After manual removal, my Zope works again.
Dieter
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )