Hello, after restarting one of my Zope servers, it fails and I get the following: ... raise DatabaseError, ( DatabaseError: The database contains records, starting at position 112192, that have time stamps 629676609.614 seconds in the future. This could lead to database corruption. Please double check your system clock! Now just how hte heck do I fix this one? (outside of modifying the code to ignore the date and hope I can fix it once it is up and running?) System info: ============ ZopeHTTPServer Latest non-CVS version DEC Alpha Linux 2.2.1 RH 5.2 (standard glibc) __ Bill
Bill Anderson wrote:
Hello, after restarting one of my Zope servers, it fails and I get the following:
... raise DatabaseError, ( DatabaseError: The database contains records, starting at position 112192, that have time stamps 629676609.614 seconds in the future. This could lead to database corruption. Please double check your system clock!
Of course, you need to check your system clock. Zope cares about time, so bad clocks can cause it problems. There should probably be an (emergency) option to make it ignore weird times.
Now just how hte heck do I fix this one? (outside of modifying the code to ignore the date and hope I can fix it once it is up and running?)
I've attached a small script that will fix broken time-stamps in a database file. This script (which is available through the public CVS) will be in 1.11. Jim -- Jim Fulton mailto:jim@digicool.com Python Powered! Technical Director (888) 344-4332 http://www.python.org Digital Creations http://www.digicool.com http://www.zope.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.
Jim Fulton wrote:
Of course, you need to check your system clock. Zope cares about time, so bad clocks can cause it problems. There should probably be an (emergency) option to make it ignore weird times.
What about the ending of daylight saving time? Should Zope be broken during an hour every year? []s -- Paulo Eduardo Neves mailto:neves@inf.puc-rio.br PUC-Rio de Janeiro
Paulo Eduardo Neves wrote:
Jim Fulton wrote:
Of course, you need to check your system clock. Zope cares about time, so bad clocks can cause it problems. There should probably be an (emergency) option to make it ignore weird times.
What about the ending of daylight saving time? Should Zope be broken during an hour every year?
Good question. (I really hate daylight savings time. ;) Fiortunately No, because the Zope database uses GMT. Jim -- Jim Fulton mailto:jim@digicool.com Technical Director (540) 371-6909 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.
BTW, the script I sent Bill solved the problem. Jim -- Jim Fulton mailto:jim@digicool.com Technical Director (540) 371-6909 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.
participants (4)
-
Bill Anderson -
Jim Fulton -
Paulo Eduardo Neves -
Pavlos Christoforou