[Zope-dev] FreeBSD, Zope and Plone

[Myroslav Opyr]

Tim McLaughlin wrote:

> Glad to see more Zopes out there are on FreeBSD... We actually haven't=20
> seen any of these issues on our systems; we're using the FreeBSD=20
> Python 2.1.1 port and Zope 2.5.1.  We're not running Plone either thoug=
h.

There was a question about a patch. I suppose the main patch location is
https://sourceforge.net/tracker/?func=3Ddetail&atid=3D305470&aid=3D554841=
&group_id=3D5470
Python tracker on SourceForge.

We also faced the problem when running Zope+CMF+CMFDecor(zpt). Patch=20
solved the problem but I think we made stack even bigger then proposed=20
in a patch. Now we have Plone site with=20
Zope-2.6a+CMF-1.3+Plone1.0beta1+AltPT+AltPTi18n. The last combination=20
have to consume huge stack! Nothing wrong with that, even when invoking=20
Plone site page as the first one after Zope start (that makes stack be=20
very deep).

Regards,

m.

> I sincerely hope BSD doesn't become second class for running Zope :/
>
> Tim
>
> Casey Duncan wrote:
>
>> In my experience, python crashes on FreeBSD are due to the default=20
>> thread stack size problem exclusively. I run Python/Zope with complex=20
>> sites all the time (not plone tho) and once patched appropriately it=20
>> never crashes unless I cause it to.
>>
>> There are two solutions to this IMHO:
>>
>> 1. Release a bug fix in Python (hasn't happened yet, but it has been=20
>> discussed several times)
>>
>> 2. Patch the FreeBSD python port. This is likely an excellent=20
>> solution and one which could also solve the large file support issue=20
>> simulaneously.
>>
>> Unless PythonLabs tells me that 2.1.4 will fix these things, I will=20
>> work on making this happen this week. I will also see how plone=20
>> behaves on my BSD box (firstly I guess).
>>
>> -Casey
>>
>> On Monday 16 September 2002 03:11 pm, alan runyan wrote:
>>
>>> I have just spent several hours trying to get plone.org back up.
>>> It appears that Plone and FreeBSD are not made for each other.
>>> I end up getting core dumps.  I applied the 'thread stack' patch.
>>> I also tried to use Python2.2.1 w/ chrism_installer branch and
>>> I get the same results.=20
>>> I am most likely going to move away from FreeBSD to Linux -
>>> which is a shame, one less FreeBSD/Zope/Plone combination
>>> running in the wild.  I know the iMeme guys have Plone running
>>> but I have seen really freakish behavior there as well.  So I am
>>> giving up.  If someone wants to hand hold me - I will try again
>>> but in a few minutes I'm moving the Data.fs file to a linux box
>>> and trying to get plone.org back up.
>>>
>>> Notes from my experience:
>>> - chrism_installer_branch is *very very* nice - thanks ChrisM.
>>>
>>> - seemingly large file support is never turned on by default in
>>> python tarballs.  I think this is a shame.  I dont know the reasons
>>> but reading the posix large file page is very scary.  Zope Corp
>>> should always enable large file support on all of their python
>>> interpreters.
>>> - Its really depressing that Python/FreeBSD/Plone have this problem.
>>> iirc yahoo.com runs lots of FreeBSD boxens running python for
>>> some of their services.  but the fact that I have spent some 3 hours
>>> trying to get all of this to work and Plone still causes python to
>>> core dump is a huge shame.  CMF sites work fine.  Plone site crash.
>>> I have never seen Plone crash on either win32 or linux.  This is
>>> FreeBSD problem.
>>>
>>> please help make Zope/Python/*BSD work together gurus - your
>>> our only hope.  I remember asking the python maintainer to up
>>> the thread stack size in python2.1.2 and his response was something
>>> like - if your requiring more than whats allocated you have serious
>>> problems.
>>>
>>> ~runyaga
>>
--=20
Myroslav Opyr
zope.net.ua <http://zope.net.ua/> =B0 Ukrainian Zope Hosting
e-mail: myroslav@zope.net.ua <mailto:myroslav@zope.net.ua>