[Zope-dev] ZEO: Abundant POSKeyErrors after packing
Our setup is: Zope 2.6, Python 2.1.3, ZEO from CVS (http://cvs.zope.org/ZEO/?only_with_tag=ZODB3-3_1-branch) This morning we encountered a baffling phenomenon. A cron job routinely packs Data.fs by calling the appropriate URL via wget. 52 minutes after packing was completed we noticed a rapid succession of POSKeyError messages in our logs. Attached are 2 typical ones. Note that every traceback from ZODB.FileStorage.modifiedInVersion was directly follow by a (corresponding?) traceback in ZEO.zrpc.connection.call. Also every POSKeyError was transient. Enough patience in reloading the requested page always resulted in a complete rendering. Stopping Zope and ZEO processes and restarting them solved the problem completely. Any guesses? Perhaps a ZEO-version more appropriate for Zope 2.6? -- 2002-11-28T08:40:40 INFO(0) zrpc:23837 zeoLoad() raised exception: 00028438 Traceback (innermost last): Module ZEO.zrpc.connection, line 226, in handle_request Module ZEO.StorageServer, line 308, in zeoLoad Module ZODB.FileStorage, line 663, in modifiedInVersion POSKeyError: 00028438 2002-11-28T08:40:40 ERROR(200) ZODB Couldn't load state for '\x00\x00\x00\x00\x0 0\x02\x848' Traceback (innermost last): Module ZODB.Connection, line 507, in setstate Module ZEO.ClientStorage, line 516, in load Module ZEO.ServerStub, line 73, in zeoLoad Module ZEO.zrpc.connection, line 322, in call POSKeyError: 00028438 -- Jo. -- Internetmanufaktur Jo Meder -- Berlin, Germany http://www.meder.de/ --- fon: ++49-30-417 17 63 33 Kollwitzstr. 75 fax: ++49-30-417 17 63 45 10435 Berlin --- mob: ++49-170- 2 98 89 97 Public GnuPG-Key -- http://www.meder.de/keys/jo-pubkey.txt ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] KeywordIndex errors
2002-11-27T16:16:26 ERROR(200) KeywordIndex unindex_object could not remove documentId -869933785 from index companies. This should not happen. exceptions.KeyError: -869933785 This usually happens when there are duplicates in the indexed keywords and the record isn't updated before unindexing. Shouldn't cause any problems, though it isn't nice. This can be easily fixed by changing the KeywordIndex' index_object method to make keywords unique before indexing. Hmm, recall that PathIndex error I reported a few days ago? That was also an unindex error, also exercised by migrating to 2.6.0. I wonder why the process of *migrating* should cause dups in the index...? seb Hi, started seeing quite a few of these showing up in one of our server's logs: -- 2002-11-27T16:16:26 ERROR(200) KeywordIndex unindex_object could not remove documentId -869933785 from index companies. This should not happen. exceptions.KeyError: -869933785 This is Zope 2.6.0, hence the total lack of traceback :-( Anyone got any idea what's going on here? cheers, Chris ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bugfix release?
Guido van Rossum wrote: That means we either waste a lot more time doing releases, or the releases become a lot more shoddy, hardly more than a snapshot from CVS. Neither sounds attractive, sorry. ...or the release process becomes automated/documented enough that neither of these happen ;-) Chris ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bugfix release?
Casey Duncan wrote: I'm assuming we will not have bug day before 2.6.1, but perhaps one shortly thereafter is in order? I'll upgrade to 2.6.2 when it comes out then ;-) Chris ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.6.0 ZMI Problem for CJK(Collector 623) patch.
On Thu, 28 Nov 2002 09:47:04 +0900 Hajime Nakagami [EMAIL PROTECTED] wrote: Zope 2.6.0 have a problem for non 'iso-8859-1' user. And Collector 623 is still incollect now. http://collector.zope.org/Zope/623 It's serious problem for CJK(I'm Japanese). So I make patch for 2.6.0. http://www005.upp.so-net.ne.jp/zope260-i18n-20021123.diff This patch seems to have a minor performance problem, that is, applying this patch, traverse() be called two times at the time of publishing. 1. ZPublisher/HTTPRequest.py - get_default_charset() - added to get default charset from the environment 2. ZPublisher/Publish.py - publish() - normal call I would like to know whether calling traverse() only to get 'default_charset' is inevitable. Any good workaround? Another thing, I'm concerning over security issues. In this patch, extra argument is added to traverse(); def traverse(self, path, response=None, validated_hook=None, auth_check=1): -- auth_check is added And called like this from get_default_charset(); object=req.traverse(req.environ['PATH_INFO'][:], auth_check=0) Putting auth_check=0 will bypass authorization check. I don't want to add such an argument, because it might bear a security issue. Any good workaround? I'm hesitating to upgrading to Zope 2.6.0, partly because of http://collector.zope.org/Zope/623. It would be greatly appreciated if this patch would be refined. Regards, Kazuya -- Kazuya Fukamachi The limits of my language are http://www.atransia.co.jp/home/ZenKai/ the limits of my world. (sorry only in Japanese) --Ludwig Wittgenstein ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] KeywordIndex errors
seb bacon wrote: 2002-11-27T16:16:26 ERROR(200) KeywordIndex unindex_object could not remove documentId -869933785 from index companies. This should not happen. exceptions.KeyError: -869933785 This usually happens when there are duplicates in the indexed keywords and the record isn't updated before unindexing. Shouldn't cause any problems, though it isn't nice. This can be easily fixed by changing the KeywordIndex' index_object method to make keywords unique before indexing. Hmm, recall that PathIndex error I reported a few days ago? That was also an unindex error, also exercised by migrating to 2.6.0. I wonder why the process of *migrating* should cause dups in the index...? The errors were reported when I was deleting object created in Zope 2.6.0 already, but that instance of Plone probably migrated 2.5 - 2.6. We are migrating Plone, not Zope right now... m. -- Myroslav Opyr zope.net.ua http://zope.net.ua/ ° Ukrainian Zope Hosting e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] KeywordIndex errors
- Original Message - From: seb bacon [EMAIL PROTECTED] Sent: Thursday, November 28, 2002 11:22 AM Subject: Re: [Zope-dev] KeywordIndex errors 2002-11-27T16:16:26 ERROR(200) KeywordIndex unindex_object could not remove documentId -869933785 from index companies. This should not happen. exceptions.KeyError: -869933785 This usually happens when there are duplicates in the indexed keywords and the record isn't updated before unindexing. Shouldn't cause any problems, though it isn't nice. This can be easily fixed by changing the KeywordIndex' index_object method to make keywords unique before indexing. Hmm, recall that PathIndex error I reported a few days ago? That was also an unindex error, also exercised by migrating to 2.6.0. I wonder why the process of *migrating* should cause dups in the index...? It shouldn't cause them, they were probably already there. The PathIndex errors resulted from a change in the api, I don't think they are related to the errors Chris was seeing. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.6.0 ZMI Problem for CJK(Collector 623) patch.
On Thu, 28 Nov 2002 18:25:26 + Toby Dickenson [EMAIL PROTECTED] wrote: Feel free to do that if it works for you, but a patch for this approach will not be accepted into the standard Zope. See this bug report for an explanation of why this contradict's Zope's current unicode approach: It seems some Russian made a similar patch to solve the same problem too: http://itconnection.ru/pipermail/zopyrus/2002-November/001388.html I hate to say it, but it seems the Zope's current unicode approach is very problematic and offensive to the Zope community outside Latin-1 world. As of late, in Japanese Zope community, 2.6.0 seems to be regarded as defective and almost all users skip it rather than upgrade from 2.5.1, as far as I know. I'm at a loss, as to what to do, what's the solution/future direction, etc. Regards, --- Heiichiro NAKAMURA [EMAIL PROTECTED] ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.6.0 ZMI Problem for CJK(Collector 623) patch.
Hi.
The right approach is to make it possible to change the title property to a
unicode string. All my custom products have this already, but it is a
deficiency in the standard Zope types such as 'Folder' that their
titles type can not be changed.
This approach is not useful for me.
I often use zope with RDB like MySQL.
generally japanese encoding text is in RDB.
so if object properties are unicode string,
I always encode it before publishing.
title tal:content=python:here.title.encode('euc-jp')TITLE/title
because, it always mix in RDB data(japanese) and
properties(python unicode string) in one page.
certainly I will be faced with this ustring problem everytime.
Japanese charactor is not ascii,
so if I do not encode ustring before publishing,raise unicode error.
if don't allow to use string type in properties, I regret that I
would continue to use zope2.5.1 or make my own monkey patches for
after this.
I'm sorry to my BAD English.
Thank you.
--
Yusei TAHARA
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
