Anthony Baxter wrote:
Jim Fulton wrote
1999-11-24T05:51:23 PANIC(300) ZODB An storage error occurred in the last phase of a two-phase commit. This shouldn't happen. The application may be in a hosed state, so we will not allow transactions to commit from here
Waaaa. This should include a traceback, but it doesn't. I wonder if there is a bug in the logging machinery.
Well, the above went to stdout - I can't find anything in any of the logs.
See doc/LOGGING.txt to see how to get stuff written to the event log file.
As the message indicates, this happens if an error occurs during the final stage of a two-phase commit. If this happens, then database integrity cannot be assured unless further writes are prevented. The only case in which I've seen this happen is if the disk fills up. Could this be happening to you?
Nope - there's plenty of free space on the disk. Where should I start looking? I'm going to force the bit of the code that generated this error to spit out a traceback...
OK, I just checked in a fix to lib/python/Zope/ZLogger/stupidFileLogger.py that should allow you to get a traceback in the log. Try applying this fix and see what you get. Jim -- Jim Fulton mailto:jim@digicool.com Technical Director (888) 344-4332 Python Powered! Digital Creations http://www.digicool.com http://www.python.org Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.