[Zope-dev] Zope crash & restart

[Jens Vagelpohl]

this particular issue is *not* solved in 2.1.3

jens


On Wednesday, May 15, 2002, at 10:00 , Myroslav Opyr wrote:

> As far as I remember the issue was solved in Python 2.1.3, wasn't it? Or
> it was GC patch?
>
> Ok, I'll try to patch sources...
>
> m.
> --
> Myroslav Opyr
> zope.net.ua * Ukrainian Zope Hosting
> e-mail: myroslav@zope.net.ua
> cell: +380 50.3174578
>
>
> On Wed, 15 May 2002, Jens Vagelpohl wrote:
>
>> python has a crashbug under FreeBSD due to FreeBSDs *tiny* thread stack
>> size.
>>
>> search the mailing list, there were posts with workarounds. 
>> unfortunately,
>>   those workarounds involve patching python sources and recompiling.
>>
>> jens
>>
>>
>> On Wednesday, May 15, 2002, at 09:50 , Myroslav Opyr wrote:
>>
>>> Hi,
>>>
>>> There is installation:
>>>
>>> Zope Version
>>>   (Zope 2.5.1 (source release, python 2.1, linux2), python 2.1.3,
>>> freebsd4)
>>> Python Version
>>>   2.1.3 (#1, May 5 2002, 06:29:09) [GCC 2.95.3 20010315 (release)
>>> [FreeBSD]]
>>> System Platform
>>>   freebsd4
>>>
>>> ZODB contains an instance of modified CMFSite (translated in Ukrainian,
>>> CMFSiteUA).
>>>
>>> System works perfectly well even on Zope 2.5.0 on Win32 platform but
>>> crashes on FreeBSD.
>>>
>>> Site was Exported (from Win32) and Imported (to FreeBSD). Local 
>>> Filesystem
>>> View folders were deleted and recreated manually.
>>>
>>> As soon as somebody tries to touch that CMFSiteUA Zope crashes and
>>> restarts. Workaround found is: to enter management interface somwhere
>>> deeper, for example /Examples/manage or /Control_Panel/manage. Then Zope
>>> loads parts of the system into RAM and appears possibility to run the
>>> site.
>>>
>>> Sooner or later, when there is sufficient time-frame to unload all 
>>> objects
>>> out of the RAM cache (no user activity), system turns back into unusable
>>> state and again there is need to bring it up with /Control_Panel/manage.
>>> .
>>> .
>>>
>>> Any hints? BTW, there is absolutely no output in debug mode. Just usual
>>> INFO(0) messages on startup. Crash and again usual messages. Watchdow
>>> process remains into memory but new child performing requests processinf
>>> are respawned. And again INFO(0) messages are flushed into stdout...
>>>
>>> Any help would be appreciated.
>>>
>>> Regards,
>>>
>>> Myroslav
>>> --
>>> Myroslav Opyr
>>> zope.net.ua * Ukrainian Zope Hosting
>>> e-mail: myroslav@zope.net.ua
>>> cell: +380 50.3174578
>>>
>>>
>>>
>>> _______________________________________________
>>> Zope-Dev maillist  -  Zope-Dev@zope.org
>>> 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  -  Zope-Dev@zope.org
> 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 )