can't start zope after upgrade Please help !!
Hi, I use zope with a Debian testing/sarge. The last running version of zope was 2.6.1-4. The last upgrade proposed was 2.6.1-7 . The post-install script of zope didn't work and the install process failed, but I tried to end the install process by hand... The other packages of the server are up to date. This new version of the zope package changes the location of apps, so I created a new instance (zopectl create), moved the data files to the new location /var/lib/zope/instance/default/var/ , restarted the server. The zope server seems to be running : the port 9173 is open and listening, and I can see the connection with netstat -ap when I try to connect it. The issue is that no page is served : when I ask for a page, I receive 0 byte in answer (the connection times out a _long_ time later). The /var/log/zope/default/Z2.log file is still empty. I don't see any error message. One zope process and several python2.1 processes are running. My production data are on this server and I don't wand to loose them... I have a copy of the data files before crash, but I don't know if I can reuse them. Could anyone help me to restart zope ?
I use zope with a Debian testing/sarge. The last running version of zope was 2.6.1-4. The last upgrade proposed was 2.6.1-7 . The post-install script of zope didn't work and the install process failed, but I tried to end the install process by hand... The other packages of the server are up to date.
This new version of the zope package changes the location of apps, so I created a new instance (zopectl create), moved the data files to the new location /var/lib/zope/instance/default/var/ , restarted the server.
The zope server seems to be running : the port 9173 is open and listening, and I can see the connection with netstat -ap when I try to connect it.
The issue is that no page is served : when I ask for a page, I receive 0 byte in answer (the connection times out a _long_ time later).
The /var/log/zope/default/Z2.log file is still empty. I don't see any error message. One zope process and several python2.1 processes are running.
My production data are on this server and I don't wand to loose them... I have a copy of the data files before crash, but I don't know if I can reuse them.
I don't know how Debian packages Zope, but here's what I would do: get the binary distribution from zope.org, install it somewhere different (like /opt), copy your non-default products and your Data.fs to that, and get things running (this should take all of ten minutes) while you straighten out the mess your packager made. (Probably remove it and reinstall it.) Then you can move things back to your package-Zope directory. If you don't need to get things running in the meantime, just get your data to a safe place, reinstall the broken package, and move your Data.fs back. I find it likely that you have a permissions problem: they often manifest in strange ways. (One even cost me $10 when it filled my log files well beyond my ISP's quota with permissions problem messages. Luckily I caught it before it did any serious damage -- to my wallet or the machine.) At least you have backups: if you want to use a distro-packaged Zope for an important purpose, be sure you can recover from the packager screwing up. (And this means regular backups.) Is 9173 the default port for Debian Zopes? Why not 8080, I wonder? --jcc
It's probably 9673, which used to be the default port for Zope 1.10. Debian probably reserves 8080 for something else. FWIW, 9673 spells 'zope' on a telephone keypad. ;-) - C On Fri, 2003-06-06 at 14:18, J Cameron Cooper wrote:
Is 9173 the default port for Debian Zopes? Why not 8080, I wonder?
--jcc
_______________________________________________ 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 )
On Fri, Jun 06, 2003 at 02:36:42PM -0400, Chris McDonough wrote:
It's probably 9673, which used to be the default port for Zope 1.10. Debian probably reserves 8080 for something else.
FWIW, 9673 spells 'zope' on a telephone keypad. ;-)
- C
It is definately 9673. I hope that it was a typo. Rationale: The former default, 8080, conflicted with proxy servers like squid, wwwoffle etc. (closes: #46015). Jim Penny
On Fri, 2003-06-06 at 14:18, J Cameron Cooper wrote:
Is 9173 the default port for Debian Zopes? Why not 8080, I wonder?
--jcc
_______________________________________________ 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 )
On Fri, 06 Jun 2003 13:18:20 -0500, J Cameron Cooper wrote
get the binary distribution from zope.org, install it somewhere different (like /opt), copy your non-default products and your Data.fs to that, Hi all,
Thank's _a_lot_ for your help ! I believe that it's more secure to restart with the archive from zope.org. I reinstalled zope this way in /home/zope/site and got all my data back, but now I have an issue reinstalling CPS, which my site is based on : I get an error : 'Not a registered directory: Products/NuxCPS/default_skins' The directory default_skins exists and is in Products/NuxCPS... Could someone explain me what then is a 'registered directory' ? And of course if someone has the genious solution, it will be very welcome ;) Following the trackback of the error. Time 2003/06/07 02:56:11.886 GMT+2 User Name (User Id) admin (admin) Request URL http://localhost:9673/manage_addProduct/NuxCPS/manage_addCPSSite Exception Type ValueError Exception Value Not a registered directory: Products/NuxCPS/default_skins Traceback (innermost last): * Module ZPublisher.Publish, line 98, in publish * Module ZPublisher.mapply, line 88, in mapply * Module ZPublisher.Publish, line 39, in call_object * Module Products.NuxCPS.CPSSite, line 81, in manage_addCPSSite * Module Products.ExternalMethod.ExternalMethod, line 231, in __call__ __traceback_info__: ((), {'langs_list': ['en', 'fr']}, (None,)) * Module /home/zope/test5x86cps/lib/python/Products/NuxCPS/Extensions/cpsinstall.py, line 444, in cpsupdate * Module Products.CMFCore.DirectoryView, line 534, in manage_addDirectoryView * Module Products.CMFCore.DirectoryView, line 502, in createDirectoryView ValueError: Not a registered directory: Products/NuxCPS/default_skins
... I reinstalled zope this way in /home/zope/site and got all my data back, but now I have an issue reinstalling CPS, which my site is based on : I get an error : 'Not a registered directory: Products/NuxCPS/default_skins' The directory default_skins exists and is in Products/NuxCPS...
Could someone explain me what then is a 'registered directory' ? And of course if someone has the genious solution, it will be very welcome ;)
Following the trackback of the error.
Time 2003/06/07 02:56:11.886 GMT+2 User Name (User Id) admin (admin) Request URL http://localhost:9673/manage_addProduct/NuxCPS/manage_addCPSSite Exception Type ValueError Exception Value Not a registered directory: Products/NuxCPS/default_skins Traceback (innermost last): * Module ZPublisher.Publish, line 98, in publish * Module ZPublisher.mapply, line 88, in mapply * Module ZPublisher.Publish, line 39, in call_object * Module Products.NuxCPS.CPSSite, line 81, in manage_addCPSSite * Module Products.ExternalMethod.ExternalMethod, line 231, in __call__ __traceback_info__: ((), {'langs_list': ['en', 'fr']}, (None,)) * Module /home/zope/test5x86cps/lib/python/Products/NuxCPS/Extensions/cpsinstall.py, line 444, in cpsupdate * Module Products.CMFCore.DirectoryView, line 534, in manage_addDirectoryView * Module Products.CMFCore.DirectoryView, line 502, in createDirectoryView ValueError: Not a registered directory: Products/NuxCPS/default_skins
I was hoping someone who knew NuxCPS would chime in, but no go I guess. This seems entirely a problem with that product, so you should take it to that community/author. I kind of guess that there's a (in CMF-speak) skins tool somewhere that needs to be told that such a directory contains skins. But I don't know. --jcc
... P tiLux wrote at 2003-6-6 14:57 +0100: My production data are on this server and I don't wand to loose them...
Do not worry. Keep a copy at a safe place.
I have a copy of the data files before crash, but I don't know if I can reuse them.
Try it.
Could anyone help me to restart zope ?
Activate Zope logging (--> "doc/LOGGING.txt") and see whether the log file contains any hints. If this does not help, start Zope with "-M m_log". This is the detailed request log file. Unlike "Z2.log" (which logs only finished requests), the detailed log file logs 4 events for any (complete) request: the request arrival with ZServer, the request delivery to Zope, the request completion by Zope and the transmittion of the complete response. This gives you precise information on where the problem lies. Dieter
participants (6)
-
Chris McDonough -
Dieter Maurer -
J Cameron Cooper -
Jim Penny -
P tiLux -
Thierry Benita