ZCatalog: Possibly corrupted Date Field Indexes in Zope 2.3.3
Hi all, We have just experienced a strange phenomena in the ZCatalog of Zope 2.3.3. Everything seems to work alright except for searches using range:min, range:max and range:min:max on field indexes indexing dates. Using ranges on field indexes with dates result in empty result sets. To solve the problem we just had to remove the ZCatalog, re add it and re index all items. The it worked perfect again. The web master for the site claims that the error occurred sometime during the night. (This might be a false observation from his account.) Anyway, undoing all transaction one day back past the supposed "event" that might have triggered the corruption didn't solve the problem. So I wonder: 1. What could have happen? 2. Could it be that something not of Date type had been indexed? 3. How could I investigate what did happen? Is there any logging capability that might trap this kind of failures? (I'm currently waiting for a CD with all log files and the corrupted Data.fs.) Thanks in advance, Johan Carlsson torped strategi och kommunikation ab johan carlsson johanc@torped.se birkagatan 9 113 36 stockholm västmannagatan 67 http://www.torped.se http://easypublisher.torped.se
Is this behaviour reproducable under a new version ? 2.4.4, 2.5.0 ? Andreas ----- Original Message ----- From: "Johan Carlsson [Torped]" <johanc@torped.se> To: <zope@zope.org> Sent: Thursday, February 21, 2002 03:09 Subject: [Zope] ZCatalog: Possibly corrupted Date Field Indexes in Zope 2.3.3 Hi all, We have just experienced a strange phenomena in the ZCatalog of Zope 2.3.3. Everything seems to work alright except for searches using range:min, range:max and range:min:max on field indexes indexing dates. Using ranges on field indexes with dates result in empty result sets. To solve the problem we just had to remove the ZCatalog, re add it and re index all items. The it worked perfect again. The web master for the site claims that the error occurred sometime during the night. (This might be a false observation from his account.) Anyway, undoing all transaction one day back past the supposed "event" that might have triggered the corruption didn't solve the problem. So I wonder: 1. What could have happen? 2. Could it be that something not of Date type had been indexed? 3. How could I investigate what did happen? Is there any logging capability that might trap this kind of failures? (I'm currently waiting for a CD with all log files and the corrupted Data.fs.) Thanks in advance, Johan Carlsson torped strategi och kommunikation ab johan carlsson johanc@torped.se birkagatan 9 113 36 stockholm västmannagatan 67 http://www.torped.se http://easypublisher.torped.se _______________________________________________ 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 )
At 06:22 2002-02-21 -0500, Andreas Jung wrote:
Is this behaviour reproducable under a new version ? 2.4.4, 2.5.0 ?
Andreas
It's a little bit to early to tell because I can't reproduce it on Zope 2.3.3. The only thing I have right now is a corrupted Data.fs, so I have to investigate it. Not having a faintest idea what I'm looking for or how to examine the Data.fs this seems a bit problematic at the moment. One approach I have considered is to truncate the Data.fs until the problem disappears and try to figure out where it when wrong. Any approach better when that would be very appreciated. Regards, Johan Carlsson
The distribution of Zope 2.5 has a new utility to check the consistence of the ZCatalog. I am not sure it will work under 2.3.3. Maybe give it a try. Andreas On Thu, Feb 21, 2002 at 05:29:16PM +0100, Johan Carlsson [Torped] wrote:
At 06:22 2002-02-21 -0500, Andreas Jung wrote:
Is this behaviour reproducable under a new version ? 2.4.4, 2.5.0 ?
Andreas
It's a little bit to early to tell because I can't reproduce it on Zope 2.3.3. The only thing I have right now is a corrupted Data.fs, so I have to investigate it.
Not having a faintest idea what I'm looking for or how to examine the Data.fs this seems a bit problematic at the moment.
One approach I have considered is to truncate the Data.fs until the problem disappears and try to figure out where it when wrong. Any approach better when that would be very appreciated.
Regards, Johan Carlsson
At 11:55 2002-02-21 -0500, you wrote:
The distribution of Zope 2.5 has a new utility to check the consistence of the ZCatalog. I am not sure it will work under 2.3.3. Maybe give it a try. Andreas
If it's not too Python 2.x dependent it might work. From 2.4 add up ZCatalog has the new pluggable indexes, but that shouldn't be a problem. As far as I'm aware field index hasn't changed? Otherwise I might be able to "mount" the Data.fs in a Zope 2.5 environment. Thanks for the tips, Johan Carlsson
participants (3)
-
Andreas Jung -
Andreas Jung -
Johan Carlsson [Torped]