Fixing a ZODB with timestamps in the future
Hi everyone, I have a Z ODB (version 2, running with 1.10.3) that got corrupted when something went wrong with my system clock, causing the Z ODB to get filled with a lot of time stamps which are stuck in the future. Is there an easy way to fix this? Do I need to go through all the records in the database and set the time backwards, or something like that? If someone has an easy way to deal with this, please let me know! --Brian
Brian Hooper wrote:
Hi everyone,
I have a Z ODB (version 2, running with 1.10.3) that got corrupted when something went wrong with my system clock, causing the Z ODB to get filled with a lot of time stamps which are stuck in the future.
Is there an easy way to fix this? Do I need to go through all the records in the database and set the time backwards, or something like that? If someone has an easy way to deal with this, please let me know!
Look at the fixbbbts.py module in the utilities directory of a Zope 2 distribution. It is intended to fix this. Note that ZODB 3 is more forgiving of time stamps in the future. (It whines in the log, but otherwise ignores them.) 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.
Hello, ZServer adds a nonstandard portnumber to the client address for each entry in var/Z2.log thus breaking visitor tracking and domain reporting capabilities of most site analysis software. I thought I would ask if there is an easier way to turn this off before I went into the code and just commented out the relevent print statements. Thanks, Matt -- Matthew Marlowe http://www.jalan.com/ (p) 909.799.3805 mmarlowe@jalan.com Jalan Network Services (f) 909.799.3285 "Quality Web Hosting, Network, Linux, and Solaris Consulting"
At 03:50 PM 7/20/99 -0700, Matthew Marlowe wrote:
ZServer adds a nonstandard portnumber to the client address for each entry in var/Z2.log thus breaking visitor tracking and domain reporting capabilities of most site analysis software. I thought I would ask if there is an easier way to turn this off before I went into the code and just commented out the relevent print statements.
Unfortunately Zserver doesn't have a flexible hit logging facility. It wouldn't be hard to make things better, but it hasn't been a high enough priority and I simply haven't had the time to get to this. I'm always open to patches. If you're interested in tackling this problem talk to me off-line. Otherwise, as everyone knows, you are always welcome to fix it yourself or pay someone (including DC) to fix it. -Amos
participants (4)
-
Amos Latteier -
Brian Hooper -
Jim Fulton -
Matthew Marlowe