PANIC(300) & FSSession?
And what does this mean? Is it as bad as I felt it was. I had to restart Zope. 2001-02-27T09:19:28 PANIC(300) ZODB A storage error occurred in the last phase of a two-phase commit. This s houldn't happen. The application may be in a hosed state, so transactions will not be allowed to commit until the site/storage is reset by a restart. Traceback (innermost last): File C:\Program Files\Zopesite\lib\python\ZODB\Transaction.py, line 296, in commit File C:\PROGRA~1\Zopesite\lib\python\Shared\DC\ZRDB\TM.py, line 122, in tpc_finish (Object: TM) File C:\Program Files\Zopesite\lib\python\Products\FSSession\FSSession.py, line 87, in _finish (Object: TM) File C:\Program Files\Zopesite\lib\python\Products\FSSession\FSSession.py, line 206, in final_commit (Object: gmisSession) OSError: [Errno 2] No such file or directory: 'C:\\Program Files\\Zopesite\\var\\FSSession\\052\\10\\12\\0521 0120924410130' NT, Zope version: Zope 2.2.5 (binary release, python 1.5.2, win32-x86) Python version: 1.5.2 (#0, Jul 30 1999, 09:52:18) [MSC 32 bit (Intel)] System Platform: win32 -- Object: gmisSession is a FSSession that I have renamed
participants (1)
-
Peter Bengtsson