Zope, FreeBSD and core dump :(
Hi, I am moving a site from my server (linux, python 2.1.3, zope 2.6.1) to hoster's machine (FreeBSD 4.x, Python 2.2.2, Zope 2.6.1 (2.6.2 tested too)) Site is accessed through Apache using mod_rewrite and VHM (at port 80) and also directly at port 8082. When i access some pages at mysite.com:80, i get === ERROR(200) zdaemon Process xxx terminated by signal SIGSERV(11) (core dumped) === and server restarts. In the browser i get Proxy Error: zero-sized reply. It never happens when i access mysite:8082. Sometimes i can access mysite:80 if i open and re-save one or another zpt through ZMI (mysite:8082) - the site remains accesible for several minutes until it dumps core again. And i noticed that some pages of the site doesn't cause server restart, and other pages did it very often. My site uses following products: PageTemplates, PythonScripts, OrderedFolder, TextIndexNG and Epoz. No CMF or Plone or whatever. There are zope/var/python.core file, but i am unfamiliar with gdb and can't get any useful info with it What is the possible causes of this segfaults? What can i do to narrow the problem? Thanks
The last time I looked at the documentation (which was awhile ago) Zope 2.6.1 didn't work with Python 2.2. Try using your older version of Python. rogerb -----Original Message----- From: zope-bounces+roger=beavans.org@zope.org [mailto:zope-bounces+roger=beavans.org@zope.org]On Behalf Of Sergey Volobuev Sent: Tuesday, September 23, 2003 8:47 AM To: zope@zope.org Subject: [Zope] Zope, FreeBSD and core dump :( Hi, I am moving a site from my server (linux, python 2.1.3, zope 2.6.1) to hoster's machine (FreeBSD 4.x, Python 2.2.2, Zope 2.6.1 (2.6.2 tested too)) Site is accessed through Apache using mod_rewrite and VHM (at port 80) and also directly at port 8082. When i access some pages at mysite.com:80, i get === ERROR(200) zdaemon Process xxx terminated by signal SIGSERV(11) (core dumped) === and server restarts. In the browser i get Proxy Error: zero-sized reply. It never happens when i access mysite:8082. Sometimes i can access mysite:80 if i open and re-save one or another zpt through ZMI (mysite:8082) - the site remains accesible for several minutes until it dumps core again. And i noticed that some pages of the site doesn't cause server restart, and other pages did it very often. My site uses following products: PageTemplates, PythonScripts, OrderedFolder, TextIndexNG and Epoz. No CMF or Plone or whatever. There are zope/var/python.core file, but i am unfamiliar with gdb and can't get any useful info with it What is the possible causes of this segfaults? What can i do to narrow the problem? Thanks _______________________________________________ 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 )
[Roger Beavans wrote (roger@beavans.org) on 9/23/03 1:58 PM]
The last time I looked at the documentation (which was awhile ago) Zope 2.6.1 didn't work with Python 2.2. Try using your older version of Python.
there is a 2.1.3 port in /usr/ports/lang/python21 i believe, and if the ports collection is up to date, it should give you a good usable version. <--> george donnelly ~ http://www.zettai.net/ ~ "Quality Zope Hosting" Shared and Dedicated Zope Hosting ~ Zope Servers ~ Zope Websites Yahoo, AIM: zettainet ~ MSN: zettainet@hotmail.com ~ ICQ: 51907738
The last time I looked at the documentation (which was awhile ago) Zope 2.6.1 didn't work with Python 2.2. Try using your older version of Python.
there is a 2.1.3 port in /usr/ports/lang/python21 i believe, and if the ports collection is up to date, it should give you a good usable version.
I asked hosting provider to install Python 2.1.3 from ports (google says that recent Python ports includes the pthreads patch) and now anything works great. Thanks.
Python 2.2.2 has some known crashbugs provoked by Zope. Use Python 2.2.3. Also, FreeBSD has a very small default thread stack size (64k), which can cause core dumps in highly recursive applications (such as Zope). This was a problem at least for Python 2.1 on BSD. I don't use BSD so I'm not sure if it carries over into the 2.2 series. See http://www.zwiki.org/PatchPython213 for more information. On Tue, 2003-09-23 at 09:58, Roger Beavans wrote:
The last time I looked at the documentation (which was awhile ago) Zope 2.6.1 didn't work with Python 2.2. Try using your older version of Python.
rogerb
-----Original Message----- From: zope-bounces+roger=beavans.org@zope.org [mailto:zope-bounces+roger=beavans.org@zope.org]On Behalf Of Sergey Volobuev Sent: Tuesday, September 23, 2003 8:47 AM To: zope@zope.org Subject: [Zope] Zope, FreeBSD and core dump :(
Hi,
I am moving a site from my server (linux, python 2.1.3, zope 2.6.1) to hoster's machine (FreeBSD 4.x, Python 2.2.2, Zope 2.6.1 (2.6.2 tested too))
Site is accessed through Apache using mod_rewrite and VHM (at port 80) and also directly at port 8082.
When i access some pages at mysite.com:80, i get === ERROR(200) zdaemon Process xxx terminated by signal SIGSERV(11) (core dumped) === and server restarts. In the browser i get Proxy Error: zero-sized reply. It never happens when i access mysite:8082.
Sometimes i can access mysite:80 if i open and re-save one or another zpt through ZMI (mysite:8082) - the site remains accesible for several minutes until it dumps core again. And i noticed that some pages of the site doesn't cause server restart, and other pages did it very often.
My site uses following products: PageTemplates, PythonScripts, OrderedFolder, TextIndexNG and Epoz. No CMF or Plone or whatever.
There are zope/var/python.core file, but i am unfamiliar with gdb and can't get any useful info with it
What is the possible causes of this segfaults? What can i do to narrow the problem?
Thanks
_______________________________________________ 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 )
_______________________________________________ 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 ) -- Chris McDonough <chrism@zope.com> Zope Corporation
[Chris McDonough wrote (chrism@zope.com) on 9/23/03 2:28 PM]
Also, FreeBSD has a very small default thread stack size (64k), which can cause core dumps in highly recursive applications (such as Zope). This was a problem at least for Python 2.1 on BSD. I don't use BSD so I'm not sure if it carries over into the 2.2 series.
this was supposedly patched and up-to-date ports collections should now have a good python 2.1.3. anyone building 2.1.3 on freebsd should read the Makefile first tho as you may want to enable some options for this. <--> george donnelly ~ http://www.zettai.net/ ~ "Quality Zope Hosting" Shared and Dedicated Zope Hosting ~ Zope Servers ~ Zope Websites Yahoo, AIM: zettainet ~ MSN: zettainet@hotmail.com ~ ICQ: 51907738
By the way, a while back someone offered to create an executable that would check for the stack space size on BSD that could be used during Zope configuration in the future. I haven't heard anything about this lately, but it would be helpful. On Tue, 2003-09-23 at 06:16, george donnelly wrote:
[Chris McDonough wrote (chrism@zope.com) on 9/23/03 2:28 PM]
Also, FreeBSD has a very small default thread stack size (64k), which can cause core dumps in highly recursive applications (such as Zope). This was a problem at least for Python 2.1 on BSD. I don't use BSD so I'm not sure if it carries over into the 2.2 series.
this was supposedly patched and up-to-date ports collections should now have a good python 2.1.3. anyone building 2.1.3 on freebsd should read the Makefile first tho as you may want to enable some options for this.
<--> george donnelly ~ http://www.zettai.net/ ~ "Quality Zope Hosting" Shared and Dedicated Zope Hosting ~ Zope Servers ~ Zope Websites Yahoo, AIM: zettainet ~ MSN: zettainet@hotmail.com ~ ICQ: 51907738
_______________________________________________ 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 ) -- Chris McDonough <chrism@zope.com> Zope Corporation
Andrew Sawyers has just created a HowTo which can be used to increase thread stack space under BSD for Python: http://www.zope.org/Members/ensane/HowTo.2003-09-24.2929 On Tue, 2003-09-23 at 11:31, Chris McDonough wrote:
By the way, a while back someone offered to create an executable that would check for the stack space size on BSD that could be used during Zope configuration in the future. I haven't heard anything about this lately, but it would be helpful.
On Tue, 2003-09-23 at 06:16, george donnelly wrote:
[Chris McDonough wrote (chrism@zope.com) on 9/23/03 2:28 PM]
Also, FreeBSD has a very small default thread stack size (64k), which can cause core dumps in highly recursive applications (such as Zope). This was a problem at least for Python 2.1 on BSD. I don't use BSD so I'm not sure if it carries over into the 2.2 series.
this was supposedly patched and up-to-date ports collections should now have a good python 2.1.3. anyone building 2.1.3 on freebsd should read the Makefile first tho as you may want to enable some options for this.
<--> george donnelly ~ http://www.zettai.net/ ~ "Quality Zope Hosting" Shared and Dedicated Zope Hosting ~ Zope Servers ~ Zope Websites Yahoo, AIM: zettainet ~ MSN: zettainet@hotmail.com ~ ICQ: 51907738
_______________________________________________ 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 ) -- Chris McDonough <chrism@zope.com> Zope Corporation
participants (4)
-
Chris McDonough -
george donnelly -
Roger Beavans -
Sergey Volobuev