Thanks. Is there a way to spot these data inconsistencies in Data.fs and remove or fix them ?
Regards, Danny -----Original Message----- From: Andreas Jung [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 06, 2008 12:31 PM To: Sinang, Danny; firstname.lastname@example.org Subject: Re: [Zope] Turning back system clock --On 6. Mai 2008 10:28:29 +0800 "Sinang, Danny" <[EMAIL PROTECTED]> wrote: > Dear All, > > The system clock of our Zope 2.7 machine accidentally got set to 2009. > We noticed this mistake 6 hours later and we decided to set back the > clock to 2008. > > How does this affect the integrity of Data.fs ? > >> From our observation : > > 1. Session write errors suddenly began to appear > > 2. Data.fs.index won't grow anymore and its timestamp remained at the > time we set back the clock > > 3. Packing the database (which was 8 GB at the time) took too long > without any signs of any Data.fs.pack file in the var folder. We > decided to restart Zope after a few minutes. > > 4. There seem to be some catalog indexing problems as our catalog > searches on a certain field doesn't work as reliably as it did before. > We tried reindexing the field and even the catalog, but it timed out > on us (lots of objects in the database). > > Has anyone here had any similar experiences ? How do I go about fixing > this ? Turning the clock back is known to result in data inconsistencies. It is is best-practice having NTP installed on all Zope machines. -aj _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )