[Zope] Urgent problem: Database and large clock skew

[Chris McDonough]

Jim,

It might be wise to just truncate the Data.fs at the point the
transactions occurred.

See http://www.zope.org/Members/itamar/CorruptedZODB



> -----Original Message-----
> From: Jim Flanagan [mailto:jimfl@colltech.com]
> Sent: Wednesday, June 28, 2000 1:46 PM
> To: zope@zope.org
> Subject: [Zope] Urgent problem: Database and large clock skew
> 
> 
> Hi,
> 
> In trying to fix a problem with Zope httpd server sockets 
> getting wedged in 
> TIME_WAIT state, I set my system clock ahead by a year, then 
> set it back. 
> Unfortunately, connections to the Zope httpd server occurred 
> while the 
> clock was set in the future, and now when I try to start 
> Zope, it dies with:
> 
> DatabaseError: The database contains records, starting at position 
> 189587919, that have time stamps 2540023.19965 seconds in the 
> future. This 
> could lead to database corruption.  Please double check your 
> system clock!
> 
> I'm using a pre-2.0 version of Zope (Though I can't determin 
> exacly which 
> version...)
> 
> Is there any way to correct insane timestamp values? I'm 
> pretty much dead 
> in the water.
> 
> Alternatively, I have found the section in BoboPOS.py where 
> this exception 
> is generated. Is it really a problem to have future 
> timestamps? What if I 
> just snipped this portion of the code out?
> 
> Please respond to jimfl@tensegrity.net.
> 
> TIA
> 
> --
> Jim Flanagan
> jimfl@tensegrity.net   http://jimfl.tensegrity.net
> 
> _______________________________________________
> 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 )
>