Yes, that's the problem. There's plenty of information on that. In my experience FreeBSD simply doesn't like Zope. Even though I tried all the workarounds, I expect a crash every now and then (every thirty or twenty days more or less). So I got used to rely on the control process to keep Zope running, because I just can't get rid of the OS. FreeBSD fans won't agree, for sure. So whether there's an ultimate success story on the issue, please share your top notch measures. (Not wanting to start a flame war here.) Ausum ----- Original Message ----- From: "AM" <maupin@pastrytech.com> To: <zope@zope.org> Sent: Tuesday, June 15, 2004 8:25 AM Subject: [Zope] Zope 2.7.0 crash on FreeBSD 5.2
Hello,
I've recently installed Python 2.3.4 and Zope 2.7.0 on FreeBSD 5.2 and moved my Data.fs over with no apparent problems (at first). Previously I was using Python 2.3.3, Zope 2.7.0, and FreeBSD 4.9 on a slightly slower machine.
However, now Zope is crashing with a segmentation fault when I try to edit one of the largest Python scripts (19k) in my site. This is a script that I last edited on the old machine. It runs fine, displays fine in the management interface, but trying to save it causes Zope to crash.
Searching online seems to indicate that I should have set a larger stack size for Python. I didn't install Python from the FreeBSD ports collection (for various reasons), but did it myself.
Does the Python stack size sound like the problem?
If it helps, gdb traceback gives me:
(and I don't know what most of this means)
#0 0x080729f3 in lookdict_string (mp=0x867e4f4, key=0x815b4e0, hash=435549560) at Objects/dictobject.c:316 #1 0x08073741 in PyDict_GetItem (op=0x867e4f4, key=0x815b4e0) at Objects/dictobject.c:498 #2 0x0805b3c0 in class_lookup (cp=0x868526c, name=0x815b4e0, pclass=0xbfaab088) at Objects/classobject.c:189 #3 0x0805b807 in instance_getattr2 (inst=0x904548c, name=0x815b4e0) at Objects/classobject.c:729 #4 0x08060c65 in instance_getattr1 (inst=0x904548c, name=0x815b4e0) at Objects/classobject.c:708
Any help is appreciated.
Aaron
_______________________________________________ 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 )