FreeBSD, Zope and Plone
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. 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
In my experience, python crashes on FreeBSD are due to the default thread stack size problem exclusively. I run Python/Zope with complex sites all the time (not plone tho) and once patched appropriately it 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 discussed several times) 2. Patch the FreeBSD python port. This is likely an excellent solution and one which could also solve the large file support issue simulaneously. Unless PythonLabs tells me that 2.1.4 will fix these things, I will work on making this happen this week. I will also see how plone 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.
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
_______________________________________________ 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 )
Glad to see more Zopes out there are on FreeBSD... We actually haven't seen any of these issues on our systems; we're using the FreeBSD Python 2.1.1 port and Zope 2.5.1. We're not running Plone either though. 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 thread stack size problem exclusively. I run Python/Zope with complex sites all the time (not plone tho) and once patched appropriately it 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 discussed several times)
2. Patch the FreeBSD python port. This is likely an excellent solution and one which could also solve the large file support issue simulaneously.
Unless PythonLabs tells me that 2.1.4 will fix these things, I will work on making this happen this week. I will also see how plone 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.
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
_______________________________________________ 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 )
-- Tim McLaughlin Chief Technology Officer Siteworx, Inc... Set your site on the future! 703.390.5421
Tim McLaughlin wrote:
Glad to see more Zopes out there are on FreeBSD... We actually haven't seen any of these issues on our systems; we're using the FreeBSD Python 2.1.1 port and Zope 2.5.1. We're not running Plone either though.
There was a question about a patch. I suppose the main patch location is https://sourceforge.net/tracker/?func=detail&atid=305470&aid=554841&group_id... Python tracker on SourceForge. We also faced the problem when running Zope+CMF+CMFDecor(zpt). Patch solved the problem but I think we made stack even bigger then proposed in a patch. Now we have Plone site with Zope-2.6a+CMF-1.3+Plone1.0beta1+AltPT+AltPTi18n. The last combination have to consume huge stack! Nothing wrong with that, even when invoking Plone site page as the first one after Zope start (that makes stack be 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 thread stack size problem exclusively. I run Python/Zope with complex sites all the time (not plone tho) and once patched appropriately it 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 discussed several times)
2. Patch the FreeBSD python port. This is likely an excellent solution and one which could also solve the large file support issue simulaneously.
Unless PythonLabs tells me that 2.1.4 will fix these things, I will work on making this happen this week. I will also see how plone 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. 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
-- Myroslav Opyr zope.net.ua <http://zope.net.ua/> ° Ukrainian Zope Hosting e-mail: myroslav@zope.net.ua <mailto:myroslav@zope.net.ua>
Hi, I noticed lots of Zope crashes with FreeBSD 4.5/Python 2.1.3/Zope 2.5.1. Where can I find that Python patch you're talking about ? Thanks in advance --Gilles ----- Original Message ----- From: "Casey Duncan" <casey@zope.com> To: "alan runyan" <runyaga@runyaga.com>; <zope-dev@zope.org> Sent: Monday, September 16, 2002 9:51 PM Subject: Re: [Zope-dev] FreeBSD, Zope and Plone In my experience, python crashes on FreeBSD are due to the default thread stack size problem exclusively. I run Python/Zope with complex sites all the time (not plone tho) and once patched appropriately it 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 discussed several times) 2. Patch the FreeBSD python port. This is likely an excellent solution and one which could also solve the large file support issue simulaneously. Unless PythonLabs tells me that 2.1.4 will fix these things, I will work on making this happen this week. I will also see how plone 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.
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
_______________________________________________ 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 )
http://216.239.51.100/search?q=cache:kbNhA3pDch4C:plone.org/documentation/th read_pthread.h/file_view+zope+stack+thread+patch+bsd&hl=en&ie=UTF-8 worked for me.. its ugly because its not a patch. but it worked fine w/ python2.1.3 and plone.org should shortly be up. we are migrating all the content.. btw: Casey I would greatly appreciate you following up on what you said about getting large file support and thread patch in ports. that would really save alot of hair cheers. ~runyaga ----- Original Message ----- From: "Gilles Lenfant" <gilles@pilotsystems.net> To: "Casey Duncan" <casey@zope.com>; "alan runyan" <runyaga@runyaga.com>; <zope-dev@zope.org> Sent: Monday, September 16, 2002 4:22 PM Subject: Re: [Zope-dev] FreeBSD, Zope and Plone
Hi,
I noticed lots of Zope crashes with FreeBSD 4.5/Python 2.1.3/Zope 2.5.1. Where can I find that Python patch you're talking about ?
Thanks in advance
--Gilles
----- Original Message ----- From: "Casey Duncan" <casey@zope.com> To: "alan runyan" <runyaga@runyaga.com>; <zope-dev@zope.org> Sent: Monday, September 16, 2002 9:51 PM Subject: Re: [Zope-dev] FreeBSD, Zope and Plone
In my experience, python crashes on FreeBSD are due to the default thread stack size problem exclusively. I run Python/Zope with complex sites all the time (not plone tho) and once patched appropriately it 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 discussed several times)
2. Patch the FreeBSD python port. This is likely an excellent solution and one which could also solve the large file support issue simulaneously.
Unless PythonLabs tells me that 2.1.4 will fix these things, I will work on making this happen this week. I will also see how plone 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.
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
_______________________________________________ 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 )
Casey Duncan wrote In my experience, python crashes on FreeBSD are due to the default thread stack size problem exclusively. I run Python/Zope with complex sites all the time (not plone tho) and once patched appropriately it 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 discussed several times) 2. Patch the FreeBSD python port. This is likely an excellent solution and one which could also solve the large file support issue simulaneously.
The second seems (to me) like a much, much simpler alternative. Particularly since it's only a bug that affects one platform. . . releasing a new version of python 2.1 just for a freebsd fix seems way overkill. -- Anthony Baxter <anthony@interlink.com.au> It's never too late to have a happy childhood.
----- Original Message ----- From: "Anthony Baxter" <anthony@interlink.com.au> To: "Casey Duncan" <casey@zope.com> Cc: "alan runyan" <runyaga@runyaga.com>; <zope-dev@zope.org> Sent: Monday, September 16, 2002 8:05 PM Subject: Re: [Zope-dev] FreeBSD, Zope and Plone
Casey Duncan wrote In my experience, python crashes on FreeBSD are due to the default
thread
stack size problem exclusively. I run Python/Zope with complex sites all the time (not plone tho) and once patched appropriately it 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 discussed several times) 2. Patch the FreeBSD python port. This is likely an excellent solution and one which could also solve the large file support issue simulaneously.
The second seems (to me) like a much, much simpler alternative. Particularly since it's only a bug that affects one platform. . . releasing a new version of python 2.1 just for a freebsd fix seems way overkill.
That is the option I intend to explore. FreeBSD's ports machinery makes this painless and invisible to the end user. -Casey
participants (6)
-
alan runyan -
Anthony Baxter -
Casey Duncan -
Gilles Lenfant -
Myroslav Opyr -
Tim McLaughlin