zope 2.4.x crashing on RH 7.x
hi setup tried both zope 2.4.0 and zope2.4.1 data migrated from another zope instance (zope2.3.3) via ChrisM export recipe at zopelabs zope runs ok for a while, but then restars .. and after a while restarts .. this goes on for a while .. with big M switch, nothing much on it. hangs on gif calls, some rdb call, some normal dtml method. got a few Aiieee! 19489 exited with error code: 11 errors in stupid.log. a search in the nipltd produced some help, but none that's applicable/workable. but all these runs ok with zope 2.3.3 thanks
bak (kedai) wrote:
hi setup tried both zope 2.4.0 and zope2.4.1 data migrated from another zope instance (zope2.3.3) via ChrisM export recipe at zopelabs
zope runs ok for a while, but then restars .. and after a while restarts .. this goes on for a while ..
with big M switch, nothing much on it. hangs on gif calls, some rdb call, some normal dtml method.
got a few
Aiieee! 19489 exited with error code: 11
This looks like the py_malloc problem in Python 2.11, which causes segmenatation faults like you're seeing. You need to recompile Python 2.11 without py_malloc. You should probably recompile zope after you've recompiled python, but I don't know if it is really necessary. -- Steve Alexander Software Engineer Cat-Box limited
On 07 Sep 2001 16:04:56 +0100, Steve Alexander wrote:
bak (kedai) wrote:
Aiieee! 19489 exited with error code: 11
This looks like the py_malloc problem in Python 2.11, which causes segmenatation faults like you're seeing. http://lists.zope.org/mailman/listinfo/zope-dev ) -- Andy Dustman PGP: 0x930B8AB6 @ .net http://dustman.net/andy I'll give spammers one bite of the apple, but they'll have to guess which bite has the razor blade in it.
(I hate that Evolution has ctrl-return as a short-cut to send a message...) On 07 Sep 2001 16:04:56 +0100, Steve Alexander wrote:
bak (kedai) wrote:
Aiieee! 19489 exited with error code: 11
This looks like the py_malloc problem in Python 2.11, which causes segmenatation faults like you're seeing.
I did some more investigation on this problem, and my conclusion was that a change in Python starting in version 2.0.1 (also in 2.1, which chronologically came out first) is causing these crashes. In a nutshell, when using O format with PyArgs_FromTupleAndKeywords() in < 2.0.1, you get a new reference, and in >= 2.0.1, you get a borrowed reference. The latter you need to Py_INCREF() if you want to keep. If you do this in < 2.0.1, you don't crash but you leak memory. See the zope-dev archives for the whole story. -- Andy Dustman PGP: 0x930B8AB6 @ .net http://dustman.net/andy I'll give spammers one bite of the apple, but they'll have to guess which bite has the razor blade in it.
Andy Dustman wrote:
(I hate that Evolution has ctrl-return as a short-cut to send a message...)
On 07 Sep 2001 16:04:56 +0100, Steve Alexander wrote:
bak (kedai) wrote:
Aiieee! 19489 exited with error code: 11
This looks like the py_malloc problem in Python 2.11, which causes segmenatation faults like you're seeing.
I did some more investigation on this problem, and my conclusion was that a change in Python starting in version 2.0.1 (also in 2.1, which chronologically came out first) is causing these crashes. In a nutshell, when using O format with PyArgs_FromTupleAndKeywords() in < 2.0.1, you get a new reference, and in >= 2.0.1, you get a borrowed reference. The latter you need to Py_INCREF() if you want to keep. If you do this in < 2.0.1, you don't crash but you leak memory. See the zope-dev archives for the whole story.
I think the problem you've found is different than this problem. My own anecdote is that I moved an app to Zope 2.4.x and Python 2.11, both compiled from source on i386 Linux. I got these segfaults every half hour or so, more or less. I recompiled python and zope, configuring python --without-py_malloc. I have had no further crashes. -- Steve Alexander Software Engineer Cat-Box limited
participants (3)
-
Andy Dustman -
bak -
Steve Alexander