If you've visited ZopeZen you might have noticed this lovely error that seems to occur intermittently..
[snip rest of traceback] * Module Products.CMFCore.CatalogTool, line 214, in searchResults * Module Products.ZCatalog.ZCatalog, line 619, in searchResults * Module Products.ZCatalog.Catalog, line 732, in searchResults * Module Products.ZCatalog.Catalog, line 480, in search * Module Products.PluginIndexes.common.UnIndex, line 365, in _apply_index * Module ZODB.Connection, line 534, in setstate
MemoryError: (Also, an error occurred while attempting to render the standard error message.)
Its:
Zope 2.6.1 (source release, python 2.1, linux2) python 2.1.3 openbsd3
I believe all the appropiate python stack patches are applied.
Any ideas?
Andy wrote @zope-dev
MemoryError: (Also, an error occurred while attempting to render the standard error message.)
I believe all the appropiate python stack patches are applied.
Hmmm. Maybe some FreeBSD patch will fix your problem. The current FreeBSD /usr/ports/lang/python21/files has the following files:
-rw-r--r-- 1 root wheel 2820 Nov 14 2002 patch-Lib:os.py -rw-r--r-- 1 root wheel 326 Jan 16 2002 patch-Misc:Makefile.pre.in -rw-r--r-- 1 root wheel 688 Nov 14 2002 patch-Modules:Setup.dist -rw-r--r-- 1 root wheel 793 Feb 6 17:44 patch-Python-thread_pthread.h-stacksize -rw-r--r-- 1 root wheel 429 Oct 19 2001 patch-setup.py -rw-r--r-- 1 root wheel 599 Apr 13 21:20 zwiki.patch
You might also check the following Zwiki threads on memory problems (all related to FreeBSD, but they may be caused by Imeme's memory limit)
- http://webseitz.fluxent.com/wiki/ZwikiFreebsdStabilityProblems
- http://zwiki.org/SiteReliability
- http://www.zwiki.org/GeneralDiscussion
Pieter cc: zwiki
MemoryError: (Also, an error occurred while attempting to render the standard error message.)
Hmmm. Maybe some FreeBSD patch will fix your problem. The current FreeBSD /usr/ports/lang/python21/files has the following files:
Thanks Pieter I'll take a look. This site was fine on Linux on Windows servers before so I believe its platform related.
Andy McKay wrote at 2003-6-17 08:47 -0700:
If you've visited ZopeZen you might have noticed this lovely error that seems to occur intermittently..
[snip rest of traceback] * Module Products.CMFCore.CatalogTool, line 214, in searchResults * Module Products.ZCatalog.ZCatalog, line 619, in searchResults * Module Products.ZCatalog.Catalog, line 732, in searchResults * Module Products.ZCatalog.Catalog, line 480, in search * Module Products.PluginIndexes.common.UnIndex, line 365, in _apply_index * Module ZODB.Connection, line 534, in setstate
MemoryError: (Also, an error occurred while attempting to render the standard error message.)
"MemoryError" would mean you have run out of virtual memory.
This may or may not be a Zope problem.
Dieter
On Tue, Jun 17, 2003 at 08:47:57AM -0700, Andy McKay wrote: | If you've visited ZopeZen you might have noticed this lovely error that | seems to occur intermittently.. | | [snip rest of traceback] | * Module Products.CMFCore.CatalogTool, line 214, in searchResults | * Module Products.ZCatalog.ZCatalog, line 619, in searchResults | * Module Products.ZCatalog.Catalog, line 732, in searchResults | * Module Products.ZCatalog.Catalog, line 480, in search | * Module Products.PluginIndexes.common.UnIndex, line 365, in | _apply_index | * Module ZODB.Connection, line 534, in setstate | | MemoryError: (Also, an error occurred while attempting to render the | standard error message.)
Just for the records, we were getting some MemoryError's on NZO, which were track down to some weird repr() handling on ZEO/ZODB code. There were also some fixes on memory leaks (an exception on a tal:repeat would leak some objects, plus there was one small leak on plone's portal_form) but none seem to be entirely related to your problem. However it could be a side effect of a memory leak. I would recommend getting ZODB from the new ZODB-3_2-branch, and plone from the Plone-1_0 branch. And if youre not afraid of running from CVS, get Zope from the 2_6-branch ;)
[]'s
On Tuesday 17 June 2003 11:47 am, Andy McKay wrote:
If you've visited ZopeZen you might have noticed this lovely error that seems to occur intermittently..
[snip rest of traceback] * Module Products.CMFCore.CatalogTool, line 214, in searchResults * Module Products.ZCatalog.ZCatalog, line 619, in searchResults * Module Products.ZCatalog.Catalog, line 732, in searchResults * Module Products.ZCatalog.Catalog, line 480, in search * Module Products.PluginIndexes.common.UnIndex, line 365, in _apply_index * Module ZODB.Connection, line 534, in setstate
MemoryError: (Also, an error occurred while attempting to render the standard error message.)
Its:
Zope 2.6.1 (source release, python 2.1, linux2) python 2.1.3 openbsd3
I believe all the appropiate python stack patches are applied.
In my experience, (at least on FreeBSD) it would simply fall over when it ran out of stack space, I don't remember ever seeing MemoryError. But I may not have been paying close enough attention ;^)
Looks like its running out of memory when a BTree subobject is being loaded. Do you have any idea how much memory the process was using when you got the error?
-Casey
Thanks for the responses everyone.
This message occured more frequently when I was showing the getNewOrRandom slot which does a few catalog searches and mucks them around. I've turned off that slot and setup a nightly restart cron.
I'm waiting for it to happen again (it hasn't yet), but it looks like the BTrees and Catalog results could be a place to start.
Its got a gig of ram and about 500 mb is free most of the time apparently, but next time it happens I'll see if I can get more info.
Just have to hurry up and wait now ;) Or wait for runyaga to visit it, he seems to have this curse with it.
There we go, occurred again.
Its definitely the manipulating of catalog results, all the crashes are happening on zcatalog searches. There is over 530 Megs of Memory free at the time.
But like I say its never occuring my other boxes so time to whip out some unit tests and the like ;)