[Zope] Re: MemoryError that brings my zope to its knees
George Donnelly wrote: the kernel limits the amount of ram a process can bind by default. try the following put this in /boot/loader.conf kern.maxdsiz=1610612736 kern.dfldsiz=1610612736 kerm.maxssiz=1610612736 Thanks for the hint George, I was able to accomplish this using only the loader.conf stuff. I checked with ulimit after a reboot and I now the data seg size is 1G. That should hold it for a while. Thanks again, Calvin -- S i x F e e t U p | Nowhere to go but open-source Silicon Valley: +1 (650) 401-8579 | Midwest: +1 (317) 861-5948 Toll-Free: 1-866-SIX-FEET mailto:[EMAIL PROTECTED] http://www.sixfeetup.com | Zope Hosting from $19.95/month ___ 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 )
[Zope] Re: MemoryError that brings my zope to its knees
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Calvin Hendryx-Parker wrote: In the last month I have started to get these errors using Zope 2.7.7 in a ZEO configuration with one client and one storage server: -- 2005-09-12T23:46:07 ERROR(200) ZODB Couldn't load state for 0x055ba7 Traceback (most recent call last): File /usr/local/Zope/lib/python/ZODB/Connection.py, line 600, in setstate self._set_ghost_state(obj, p) File /usr/local/Zope/lib/python/ZODB/Connection.py, line 639, in _set_ghost_state state = unpickler.load() MemoryError -- 2005-09-12T23:46:07 ERROR(200) SiteError Error while logging Traceback (most recent call last): File /usr/local/Zope/lib/python/Products/SiteErrorLog/SiteErrorLog.py, line 142, in raising tb_text = ''.join( MemoryError Sometimes I see this too: -- 2005-09-06T15:23:30 ERROR(200) ZServer uncaptured python exception, closing channel select-trigger (pipe) at bd9104c (exceptions.MemoryError: [/usr/local/lib/python2.3/asyncore.py|read|69] [/usr/local/lib/python2.3/asyncore.py|handle_read_event|390] [/usr/local/Zope/lib/python/ZServer/medusa/thread/select_trigger.py|handle_read|77] [/usr/local/lib/python2.3/asyncore.py|recv|342] [/usr/local/lib/python2.3/asyncore.py|recv|523]) That is not a problem -- some client disconnected before Zope finished processing the request. And this one also brings the show down: -- 2005-09-06T05:35:51 ERROR(200) zrpc:30832 can't decode message: (M2'K\x00U\x06.reply(TW\x00\x01\x00((U\tOFS.Imageq\x01U... -- 2005-09-06T05:35:51 ERROR(200) zrpc-conn(C):localhost:6100 Error caught in asyncore Traceback (most recent call last): File /usr/local/lib/python2.3/asyncore.py, line 69, in read obj.handle_read_event() File /usr/local/lib/python2.3/asyncore.py, line 390, in handle_read_event self.handle_read() File /usr/local/Zope/lib/python/ZEO/zrpc/smac.py, line 217, in handle_read self.message_input(msg) File /usr/local/Zope/lib/python/ZEO/zrpc/connection.py, line 339, in message_input msgid, flags, name, args = self.marshal.decode(message) File /usr/local/Zope/lib/python/ZEO/zrpc/marshal.py, line 39, in decode return unpickler.load() # msgid, flags, name, args MemoryError It completely locks up the zope until I restart. I added more RAM to the box and also bumped up the zeo cache-size to 100MB and 1 objects in the zope.conf. I also changed over from binding to an external ethernet interface and bound the zeo stuff to the localhost interface. Any ideas on other things I could try? - Try 'memtest' or an equivalent on the box to verify that you don't have a flaky RAM chip. - If you are RAM constrained, *reduce* the number of objects in the connection cache; more objects in that cache requires more RAM. Leaving the on-disk cache size high shouldn't be a problem. - Add swap space, if possible (swapping will be painful, but better than a lockup). Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDJqbB+gerLs4ltQ4RAj4HAJ4vCNeuoqIH8kDXbVzp6YTbjDn2LgCgqnzo bNaH6hDz9QBA5gCg+xcCyCs= =osoi -END PGP SIGNATURE- ___ 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 )
[Zope] Re: MemoryError that brings my zope to its knees
On Sep 13, 2005, at 12:00 PM, Pascal Peregrina wrote: What's the amount of RAM you have ? When we started having this problem the box only had 1GB of RAM so we replaced that RAM completely and put in a fresh 4GB of RAM to hopefully get rid of the problem. This box is also running 3 other Zope instances, but the other don't exhibit this problem. This instance has 15 plone site instances in it. The others only have a couple plone sites each. This problem will happen and there will still be 1GB of free RAM and it hasn't touched the swap at all. We are running FreeBSD 4.10 on this box. Have you changed the default pool-size in the zodb section ? I'm assuming it isn't changed since it isn't in our zope.conf. Must be a newer config that we didn't have from an old zope that this one was upgraded from. Here are the details from the Cache Parameters tab in the ZMI on this ZEO instance: Total number of objects in the database 282934 Total number of objects in memory from all caches6512 Target number of objects in memory per cache1 Total number of objects in each cache: Cache Name Number of active objectsTotal active and non-active objects Connection at 09e5684c604818746 Connection at 0e92902c464 1249 Total 6512 Thanks, Calvin -- S i x F e e t U p | Nowhere to go but open-source Silicon Valley: +1 (650) 401-8579 | Midwest: +1 (317) 861-5948 Toll-Free: 1-866-SIX-FEET mailto:[EMAIL PROTECTED] http://www.sixfeetup.com | Zope Hosting from $19.95/month ___ 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 )
[Zope] Re: MemoryError that brings my zope to its knees
Pascal Peregrina wrote: That looks wierd... Has the instance been running for a while when you copied the content of the Cache Parameters tab ? I would have expected many more connections (instead of just 2). Can you give us your zserver-threads value (zope.conf) ? It is not set so I assume it should be the default, but the default is supposed to be 4. Would you suggest raising this number? Thanks, Calvin -- S i x F e e t U p | Nowhere to go but open-source Silicon Valley: +1 (650) 401-8579 | Midwest: +1 (317) 861-5948 Toll-Free: 1-866-SIX-FEET mailto:[EMAIL PROTECTED] http://www.sixfeetup.com | Zope Hosting from $19.95/month ___ 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 )
[Zope] Re: MemoryError that brings my zope to its knees
This problem will happen and there will still be 1GB of free RAM and it hasn't touched the swap at all. We are running FreeBSD 4.10 on this box. the kernel limits the amount of ram a process can bind by default. try the following put this in /boot/loader.conf kern.maxdsiz=1610612736 kern.dfldsiz=1610612736 kerm.maxssiz=1610612736 put the following into your kernel conf file, rebuild your kernel and reboot: options MAXDSIZ=(768*1024*1024) options MAXSSIZ=(256*1024*1024) options DFLDSIZ=(768*1024*1024) the values are examples only, you will need to play with them to find the right ones. keep in mind that the wrong ones, e if you put them too close to the amount of physical ram in the box could cause the box not to boot. hth ___ 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 )
