Retracting Zope 2.9.7, Zope 2.10.3 releases because of a "zopectl start" problem
I decided to retractthe latest 2.9.7 and Zope 2.10.3 releases for now because of this problem: <http://mail.zope.org/pipermail/zope/2007-March/171086.html> I could confirm that "zopectl start" does not work properly. zdaemon spawns the second process however this one seems to go own immediately. Unfortunately I could not find the reason so far. Any help will be appreciated. Andreas
According to Andreas Jung:
I decided to retractthe latest 2.9.7 and Zope 2.10.3 releases for now because of this problem:
<http://mail.zope.org/pipermail/zope/2007-March/171086.html>
I could confirm that "zopectl start" does not work properly. zdaemon spawns the second process however this one seems to go own immediately. Unfortunately I could not find the reason so far. Any help will be appreciated.
At the risk of saying something obvious... "strace" showed, that the spawned process exits with raise ValueError('No REQUEST parameter in callable signature') which is part of the "postonly(callable)" function in lib/python/AccessControl/requestmethod.py. Wasnt this part of the hotfix? \wlang{} -- Willi.Langenberger@wu-wien.ac.at Fax: +43/1/31336/9207 Zentrum fuer Informatikdienste, Wirtschaftsuniversitaet Wien, Austria
Hello, Le 26/03/07 18:38, Willi Langenberger a écrit :
According to Andreas Jung:
I decided to retract the latest 2.9.7 and Zope 2.10.3 releases for now because of this problem:
<http://mail.zope.org/pipermail/zope/2007-March/171086.html>
I could confirm that "zopectl start" does not work properly. [...]
At the risk of saying something obvious...
"strace" showed, that the spawned process exits with
raise ValueError('No REQUEST parameter in callable signature') [...]
I guess that someone has already found this too, but I share it nonetheless: 'ApplicationManager.manage_restart()' in 'lib/python/App/ApplicationManager.py' does not have any 'REQUEST' parameter. The new 'postonly()' function therefore raise the above mentionned error. Changing the method signature to: manage_restart(self, URL1, REQUEST=None): makes Zope start. 'REQUEST' is not used in this method, though. However, it is also not used in 'manage_shutdown()' but appears in its signature. I guess that adding it to 'manager_restart()' should not have any side-effect. Regards, -- Damien Baty Pilot Systems - 9, rue Desargues - 75011 Paris Tél : +33 (0)1 44 53 05 55 - http://www.pilotsystems.net Hébergement Zope et Plone gratuit - http://www.objectis.org
On 3/26/07, Damien Baty <damien@pilotsystems.net> wrote:
manage_restart(self, URL1, REQUEST=None):
makes Zope start. 'REQUEST' is not used in this method, though. However, it is also not used in 'manage_shutdown()' but appears in its signature. I guess that adding it to 'manager_restart()' should not have any side-effect.
@postonly uses the REQUEST parameter, that's why it demands the parameter being present. Tres Seaver added the decorators to the Control_Panel and must've missed the REQUEST parameter on manage_restart, which only comes into effect when running the zope process with zopectl start. -- Martijn Pieters
On 3/26/07, Martijn Pieters <mj@zopatista.com> wrote:
Tres Seaver added the decorators to the Control_Panel and must've missed the REQUEST parameter on manage_restart, which only comes into effect when running the zope process with zopectl start.
Fixed on the trunk, and the 2.8, 2.9 and 2.10 branches, my servers start fine with zopectl start. -- Martijn Pieters
--On 26. März 2007 20:21:09 +0200 Martijn Pieters <mj@zopatista.com> wrote:
On 3/26/07, Damien Baty <damien@pilotsystems.net> wrote:
manage_restart(self, URL1, REQUEST=None):
makes Zope start. 'REQUEST' is not used in this method, though. However, it is also not used in 'manage_shutdown()' but appears in its signature. I guess that adding it to 'manager_restart()' should not have any side-effect.
@postonly uses the REQUEST parameter, that's why it demands the parameter being present.
Tres Seaver added the decorators to the Control_Panel and must've missed the REQUEST parameter on manage_restart, which only comes into effect when running the zope process with zopectl start.
The penalty for this bug: two bottles of wine. The workaround is to add REQUEST as optional parameter to manage_restart()? Andreas
On 3/26/07, Andreas Jung <lists@zopyx.com> wrote:
The penalty for this bug: two bottles of wine.
You know where to send the bill. ;)
The workaround is to add REQUEST as optional parameter to manage_restart()?
No, it's 'svn up' now, as I fixed it already. :) -- Martijn Pieters
--On 26. März 2007 20:54:55 +0200 Martijn Pieters <mj@zopatista.com> wrote:
On 3/26/07, Andreas Jung <lists@zopyx.com> wrote:
The penalty for this bug: two bottles of wine.
You know where to send the bill. ;)
The workaround is to add REQUEST as optional parameter to manage_restart()?
No, it's 'svn up' now, as I fixed it already. :)
Tnx for the fix. I am tagging and building the tar-balls right now. Andreas
New tar-balls are now available for download. I removed the warning messages from the download pages and the zope.org frontpage. Thanks to Martijn and Michael for jumping in! Andreas --On 26. März 2007 16:53:06 +0200 Andreas Jung <lists@zopyx.com> wrote:
I decided to retractthe latest 2.9.7 and Zope 2.10.3 releases for now because of this problem:
<http://mail.zope.org/pipermail/zope/2007-March/171086.html>
I could confirm that "zopectl start" does not work properly. zdaemon spawns the second process however this one seems to go own immediately. Unfortunately I could not find the reason so far. Any help will be appreciated.
Andreas
participants (4)
-
Andreas Jung -
Damien Baty -
Martijn Pieters -
Willi Langenberger