ZOPE 2.6.1 Released Zope 2.6.1 represents a development step in the next Zope release formed with a large number of community contributions. You may download Zope 2.6.1 from Zope.org: http://www.zope.org/Products/Zope/2.6.1/ Users of the Zope source release should note that Python 2.1.3 is now the required platform. Python 2.1.3 includes a fix to an issue that could cause crashes in Zope. Particular features of interest in Zope 2.6.1: * Catlog changes to speed sorting and lower memory consumption * ZODB Deadlock avoidance, fixed store order * BTree based indexes for FileStorage * Fixes for the rfc822 timezone / locale bugs in Zope 2.6.0 * Fixes for collector issues 322, 256, 479, 561, 595, 597, 640, 646, 650, 651, 671, 685, 686, 694, 696, 697, 699, 700, 703, 714, 721, 730, 736, 740, 763, 771 For more information on what is new in this release, see the CHANGES.txt and HISTORY.txt files for the release: * http://www.zope.org/Products/Zope/2.6.1/CHANGES.txt * http://www.zope.org/Products/Zope/2.6.1/HISTORY.txt For more information on the available Zope releases, guidance for selecting the right distribution and installation instructions, please see: http://www.zope.org/Documentation/Misc/InstallingZope.html -- Matt Kromer Zope Corporation http://www.zope.com/
On Friday 07 February 2003 22:14, Matthew T. Kromer wrote:
ZOPE 2.6.1 Released
...and it crashes with SIGHUP as well as 2.6.x Any-Beta does, then restart its daemon again. :-( Stupid log just tells me, that: Z2 Caught signal SIGHUP ... Z2 Restarting ERROR(200) zdaemon Process 27147 terminated normally, exit status 1 ZOPE 2.5.x much more stable yet, but has serious problems in stability with ZODB and sessions. :( -- Regards, Bogdan Woe unto them that rise up early in the morning -- Isaiah 5:11
--On Montag, 10. Februar 2003 13:42 +0200 "Bo M. Maryniuck" <b.maryniuk@forbis.lt> wrote:
On Friday 07 February 2003 22:14, Matthew T. Kromer wrote:
ZOPE 2.6.1 Released
...and it crashes with SIGHUP as well as 2.6.x Any-Beta does, then restart its daemon again. :-( Stupid log just tells me, that:
Z2 Caught signal SIGHUP ... Z2 Restarting ERROR(200) zdaemon Process 27147 terminated normally, exit status 1
ZOPE 2.5.x much more stable yet, but has serious problems in stability with ZODB and sessions. :(
You should provide detailed informations about your operating system, Python version etc. Complaining about crashes does not really help solving the reasons of the crashes. -aj
On Monday 10 February 2003 13:48, Andreas Jung wrote:
You should provide detailed informations about your operating system, Python version etc. Complaining about crashes does not really help solving the reasons of the crashes.
Well, since I can't reproduce this error, I can't tell you anything more, except that my OS is Linux SuSE 8.0 Pro and Zope was built (installed) from a binary tarball. After this excellent fun time I also have one record with "SIGHUP" in my stupid.log (what is actually simple Zope STDERR). Reproduce this crash again I can't. Perhaps I just something missed to tell you more? -- Regards, Bogdan Those parts of the system that you can hit with a hammer (not advised) are called hardware; those program instructions that you can only curse at are called software. -- Levitating Trains and Kamikaze Genes: Technological Literacy for the 1990's.
Well, Zope 2.6.1b2 and 2.6.1 are the same, so your observation that a problem in 2.6.1b2 is also in 2.6.1 would be correct. I fail to see any pending or rejected issues regarding SIGHUP in the Zope collector. I don't see how we are supposed to fix bugs that nobody has reported to the collector. If it is in the collector, please enlighten us where to find it. More information about the specific behavior you are experiencing, your environment and the exact steps to reproduce it would also be most helpful. -Casey On Monday 10 February 2003 06:42 am, Bo M. Maryniuck wrote:
On Friday 07 February 2003 22:14, Matthew T. Kromer wrote:
ZOPE 2.6.1 Released
...and it crashes with SIGHUP as well as 2.6.x Any-Beta does, then restart its daemon again. :-( Stupid log just tells me, that:
Z2 Caught signal SIGHUP ... Z2 Restarting ERROR(200) zdaemon Process 27147 terminated normally, exit status 1
ZOPE 2.5.x much more stable yet, but has serious problems in stability with ZODB and sessions. :(
-- Regards, Bogdan
Woe unto them that rise up early in the morning -- Isaiah 5:11
On Monday 10 February 2003 18:42, Casey Duncan wrote:
If it is in the collector, please enlighten us where to find it. More information about the specific behavior you are experiencing, your environment and the exact steps to reproduce it would also be most helpful.
No, it is not in collector. Probably. :-) The most pain is crashes rarely and quite randomly so I can't reproduce and catch crashes. All the info I can get is just a "SIGHUP" and that's all. :( For example, I can work whole day, but at evening when I went cofee, it was already restarted. Log's sais just "SIGHUP" and nothing more... OS: Linux SuSE 8.0 Pro Zope: Installed from a binary package -- Regards, Bogdan MCSE == Minesweeper Consultant / Solitaire Expert
On Monday 10 February 2003 4:54 pm, Bo M. Maryniuck wrote:
No, it is not in collector. Probably. :-) The most pain is crashes rarely and quite randomly so I can't reproduce and catch crashes. All the info I can get is just a "SIGHUP" and that's all.
Im not sure what problem you are reporting. Mishandling a SIGHUP? yes, this is messy at the moment. This area is rewritten in 2.7.x and there is a cvs branch that merges cleanly with 2.6.x The branch is something like toby-clean-shutdown-branch; I dont have cvs access right now to check the exact name. Or are you saying that zope is appearing to handle a SIGHUP without you intentionally sending it? -- Toby Dickenson http://www.geminidataloggers.com/people/tdickenson
Bo M. Maryniuck wrote at 2003-2-10 13:42 +0200:
On Friday 07 February 2003 22:14, Matthew T. Kromer wrote:
ZOPE 2.6.1 Released
...and it crashes with SIGHUP as well as 2.6.x Any-Beta does, then restart its daemon again. :-( Stupid log just tells me, that:
Z2 Caught signal SIGHUP ... Z2 Restarting ERROR(200) zdaemon Process 27147 terminated normally, exit status 1
ZOPE 2.5.x much more stable yet, but has serious problems in stability with ZODB and sessions. :( This is not a Zope problem!
Your environment decides to send Zope a SIGHUP signal (signal 1). It is correct that Zope dies on this signal. Unix operating systems usually send a SIGHUP signal when the control terminal is closed. The command "nohup" (--> "man" pages) is usually used to cope with this fact.... Dieter
On Monday 10 February 2003 21:40, Dieter Maurer wrote:
Your environment decides to send Zope a SIGHUP signal (signal 1). It is correct that Zope dies on this signal. Unix operating systems usually send a SIGHUP signal when the control terminal is closed. The command "nohup" (--> "man" pages) is usually used to cope with this fact....
Dieter, I know what SIGHUP and "man" pages means since I dont know what "MS Windows" and "Microsoft" is. ;-) OTOH, it is not quite correct since I start it with nohup and ampersand "&" in my /etc/init.d/zope script. And it even does not crashes when weather is quite ok. ;-) For example, I'm happy already third day: Zope still works, but I'm sitting like on a bomb -- when it will crash next time? -- Regards, Bogdan Q: Why do mountain climbers rope themselves together? A: To prevent the sensible ones from going home.
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Bo M. Maryniuck Sent: Wednesday, February 12, 2003 2:47 AM To: Dieter Maurer Cc: zope@zope.org Subject: Re: [Zope] Zope 2.6.1 Released
On Monday 10 February 2003 21:40, Dieter Maurer wrote:
Your environment decides to send Zope a SIGHUP signal (signal 1). It is correct that Zope dies on this signal. Unix operating systems usually send a SIGHUP signal when the control terminal is closed. The command "nohup" (--> "man" pages) is usually used to cope with this fact....
Dieter, I know what SIGHUP and "man" pages means since I dont know what "MS Windows" and "Microsoft" is. ;-) OTOH, it is not quite correct since I start it with nohup and ampersand "&" in my /etc/init.d/zope script. And it even does not crashes when weather is quite ok. ;-) For example, I'm happy already third day: Zope still works, but I'm sitting like on a bomb -- when it will crash next time?
Dieter's point is that neither the program nor the OS will autogenerate a sig hup. HUP is not like a segv that signals a program fault. Something external to zope is to blame for your sig hup. Most often, this is caused by people not reading the man page for nohup. PS. Please post in ASCII only.
On Wednesday 12 February 2003 19:03, Charlie Reiman wrote:
Dieter's point is that neither the program nor the OS will autogenerate a sig hup. HUP is not like a segv that signals a program fault. Something external to zope is to blame for your sig hup. Most often, this is caused by people not reading the man page for nohup.
In my previous post I said I've tried to _use_ nohup since Zope was sighup'ed and nothing changed. OTOH, it still works OK...
PS. Please post in ASCII only. Sorry? I never use MIME messages. ;-)
-- Regards, Bogdan I used to think I was indecisive, but now I'm not so sure.
Hello, what is the reason, why the Zope 2.6.1 is not being bundled with the current Python release 2.2? Is a switch to python 2.2 planned for one of the next releases? Some new Python libraries like PythonMagick require python 2.2. Therefore it's difficult to use them with zope. Thanks, Ulla. "Matthew T. Kromer" schrieb: ...
Users of the Zope source release should note that Python 2.1.3 is now the required platform. Python 2.1.3 includes a fix to an issue that could cause crashes in Zope.
--On Dienstag, 11. Februar 2003 11:29 +0100 Ulla Theiss <u.theiss@eurodata.de> wrote:
Hello,
what is the reason, why the Zope 2.6.1 is not being bundled with the current Python release 2.2?
This is an FAQ. 2.6.X requires Python 2.1.3, Zope 2.7 requires 2.2. Zope 2.6.1 is known to run with Python 2.2.2 but it is officially not supported. -aj
participants (8)
-
Andreas Jung -
Bo M. Maryniuck -
Casey Duncan -
Charlie Reiman -
Dieter Maurer -
Matthew T. Kromer -
Toby Dickenson -
Ulla Theiss