Re: no more SIG11 --without-pymallog --without-cycle-gc (was Re: [Zope-dev] Bravery Zope 2.5 Testers)
same for me, no more crashes - but zope needs very much memory (logo :-(() I will try know python 2.1.2. Leonardo Rochael Almeida wrote: 1008351449.5381.3.camel@spitfire"> Hi folks,I also tried the CVS ExtensionClass.h but it didn't help. We keptgetting the SIG11's.However, after reading all comments on this problem report onsourceforge:http://sourceforge.net/tracker/?func=detailatid=105470aid=471942group_id=5470pointed out in this list by Joseph Wayne Norton, and the diff -u betweenthe CVS ExtensionClass.h and the one that came with zope 2.4.3, Idecided to try recompiling python --without-cycle-gc (in addidtion to--without-pymalloc, which we used before causing an increase in timebetween restarts from 15 min to 40 min).Now our zope is running for "17 hours 29 min 40 sec" (pasted from theControl_Panel) without a single SIG11, YAY!!!I strongly recommend anyone running into these "Aiieee! 54321 exitedwith er ror code: 11 " to recompile their pythons --without-cycle-gc" tosee if the SIGSEGVs go away. Maybe even for Stefano Noferi's script?Throw in a --without-pymalloc for good measure :-)Now our zope is probably slowly leaking some cycles, but what the heck,I can live with restarting zope once per week. With ZEO it comes back in2 seconds anyway :-) Cheers, LeoPS: No, I have no intention to check if --with-pymalloc--without-cycle-gc also works :-)On Wed, 2001-12-12 at 19:57, Matthew T. Kromer wrote: OK, I am formulating a hypothesis that if you replace ExtensionClass.h in Zope 2.4 and Zope 2.5 with the following one:http://cvs.zope.org/~checkout~/Zope/lib/Components/ExtensionClass/src/ExtensionClass.h?rev=1.16.140.2content-type=text/plain(Which goes in lib/Components/ExtensionClass/src/ExtensionClass.h btw)and rebuild zope python2.1 wo_pcgi.pyand rebuld any other modules you may have which depend on extension classthat some of the segfaults could go away.[...] regards Harald Koschinski_FRIATEC AktiengesellschaftInformationssysteme und OrganisationTel. 0621 - 486 - 1454Fax. 0621 - 486 - 1840Steinzeugstrasse 50mailto:[EMAIL PROTECTED]D-68229 Mannheim
Re: no more SIG11 --without-pymallog --without-cycle-gc (was Re: [Zope-dev] Bravery Zope 2.5 Testers)
Leonardo Rochael Almeida wrote: On a related note, when is Zope 2.4.4 comming out? Post Python 2.1.2 final. :) Probably very shortly therafter. ___ 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: no more SIG11 --without-pymallog --without-cycle-gc (was Re: [Zope-dev] Bravery Zope 2.5 Testers)
Matthew T. Kromer wrote: Post Python 2.1.2 final. :) Probably very shortly therafter. When is Python 2.1.2 final out?! 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: no more SIG11 --without-pymallog --without-cycle-gc (was Re: [Zope-dev] Bravery Zope 2.5 Testers)
Today. See http://www.python.org. But give us a little time. ;-) Chris Withers wrote: Matthew T. Kromer wrote: Post Python 2.1.2 final. :) Probably very shortly therafter. When is Python 2.1.2 final out?! 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 ) ___ 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 )
no more SIG11 --without-pymallog --without-cycle-gc (was Re:[Zope-dev] Bravery Zope 2.5 Testers)
Hi folks, I also tried the CVS ExtensionClass.h but it didn't help. We kept getting the SIG11's. However, after reading all comments on this problem report on sourceforge: http://sourceforge.net/tracker/?func=detailatid=105470aid=471942group_id=5470 pointed out in this list by Joseph Wayne Norton, and the diff -u between the CVS ExtensionClass.h and the one that came with zope 2.4.3, I decided to try recompiling python --without-cycle-gc (in addidtion to --without-pymalloc, which we used before causing an increase in time between restarts from 15 min to 40 min). Now our zope is running for 17 hours 29 min 40 sec (pasted from the Control_Panel) without a single SIG11, YAY!!! I strongly recommend anyone running into these Aiieee! 54321 exited with error code: 11 to recompile their pythons --without-cycle-gc to see if the SIGSEGVs go away. Maybe even for Stefano Noferi's script? Throw in a --without-pymalloc for good measure :-) Now our zope is probably slowly leaking some cycles, but what the heck, I can live with restarting zope once per week. With ZEO it comes back in 2 seconds anyway :-) Cheers, Leo PS: No, I have no intention to check if --with-pymalloc --without-cycle-gc also works :-) On Wed, 2001-12-12 at 19:57, Matthew T. Kromer wrote: OK, I am formulating a hypothesis that if you replace ExtensionClass.h in Zope 2.4 and Zope 2.5 with the following one: http://cvs.zope.org/~checkout~/Zope/lib/Components/ExtensionClass/src/ExtensionClass.h?rev=1.16.140.2content-type=text/plain (Which goes in lib/Components/ExtensionClass/src/ExtensionClass.h btw) and rebuild zope python2.1 wo_pcgi.py and rebuld any other modules you may have which depend on extension class that some of the segfaults could go away. [...] -- Ideas don't stay in some minds very long because they don't like solitary confinement. ___ 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 )
