Help! Zope Crashed and will not start up again!
Hello folks, I'm baffled by a problem we are having with our site and would appreciate any help. We've been running Zope 2.5.1 for quite a while now without any interruption. Due to this stability, I haven't dealt with nuts and bolts sorts of issues and could really use some assistance. Seemingly out of the blue, Zope crashed. When I try to run the start script, it gets stuck on the following error: ========== /home/lrc/lib/python/SearchIndex/__init__.py:19: DeprecationWarning: The usage of the SearchIndex package is deprecated since Zope 2.4. This package is only kept for backwards compatibility for a while and will go away in a future release. Please use instead the re-factored modules in Products/PluginIndexes. warnings.warn("The usage of the SearchIndex package is deprecated since \ ========== I have seen this message before, but I've ignored it because Zope usually starts right up afterwards and runs just fine. Now it won't get past that message and I find myself in an emergency situation. Does anyone know enough about the Zope startup routine to help point me in the right direction? I greatly appreciate any advice at all. Thanks, Dan
warnings.warn("The usage of the SearchIndex package is deprecated since \
==========
I have seen this message before, but I've ignored it because Zope usually starts right up afterwards and runs just fine. Now it won't get past that message and I find myself in an emergency situation. Does anyone know enough about the Zope startup routine to help point me in the right direction?
This is a *warning*, not an error. If your Zope won't start up something else is wrong. This warning will not prevent Zope from starting. jens
On Thu, Jul 08, 2004 at 11:19:53AM -0400, Jens Vagelpohl wrote:
warnings.warn("The usage of the SearchIndex package is deprecated since \
==========
I have seen this message before, but I've ignored it because Zope usually starts right up afterwards and runs just fine. Now it won't get past that message and I find myself in an emergency situation. Does anyone know enough about the Zope startup routine to help point me in the right direction?
This is a *warning*, not an error. If your Zope won't start up something else is wrong. This warning will not prevent Zope from starting.
+1. The fact that that's where things freeze up is a red herring. if you really didn't change anything about your zope installation, I have to wonder what else could have changed on your system... What OS are you running on? (be specific.) It wouldn't happen to be a semi-recent version of RedHat Linux, would it? -- Paul Winkler http://www.slinkp.com
We're running on RedHat 7.3, Zope 2.5.1 with Python 2.1.3. The only change I can think of was that we created a "zope" user to install the instance. It looks like the zope user had been removed. Creating a new zope user seemed to fix the problem. Does this make any sense? We've switched to the backup server, and we're calling the problem an "opportunity" to upgrade to 2.7.1. Hopefully we won't run into an entirely new set of problems with that. Much obliged, Dan On Jul 8, 2004, at 12:36 PM, Paul Winkler wrote:
On Thu, Jul 08, 2004 at 11:19:53AM -0400, Jens Vagelpohl wrote:
warnings.warn("The usage of the SearchIndex package is deprecated since \
==========
I have seen this message before, but I've ignored it because Zope usually starts right up afterwards and runs just fine. Now it won't get past that message and I find myself in an emergency situation. Does anyone know enough about the Zope startup routine to help point me in the right direction?
This is a *warning*, not an error. If your Zope won't start up something else is wrong. This warning will not prevent Zope from starting.
+1. The fact that that's where things freeze up is a red herring.
if you really didn't change anything about your zope installation, I have to wonder what else could have changed on your system... What OS are you running on? (be specific.) It wouldn't happen to be a semi-recent version of RedHat Linux, would it?
--
Paul Winkler http://www.slinkp.com _______________________________________________ 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 )
I use RedHat 7.3, Zope 2.5.1 with Python 2.1.3 behind Pound in some of our configurations and know it to be stable. The removal of the zope user could easily cause protection problems. If you are running Zope on port 80, there's a bit of a fancy shuffle since access to low ports (<1024) needs root access, but zope itself is best run as a normal user. On Thu, 8 Jul 2004, Dan Gaibel wrote:
We're running on RedHat 7.3, Zope 2.5.1 with Python 2.1.3.
The only change I can think of was that we created a "zope" user to install the instance. It looks like the zope user had been removed. Creating a new zope user seemed to fix the problem. Does this make any sense?
We've switched to the backup server, and we're calling the problem an "opportunity" to upgrade to 2.7.1. Hopefully we won't run into an entirely new set of problems with that.
Much obliged,
Dan
On Jul 8, 2004, at 12:36 PM, Paul Winkler wrote:
On Thu, Jul 08, 2004 at 11:19:53AM -0400, Jens Vagelpohl wrote:
warnings.warn("The usage of the SearchIndex package is deprecated since \
==========
I have seen this message before, but I've ignored it because Zope usually starts right up afterwards and runs just fine. Now it won't get past that message and I find myself in an emergency situation. Does anyone know enough about the Zope startup routine to help point me in the right direction?
This is a *warning*, not an error. If your Zope won't start up something else is wrong. This warning will not prevent Zope from starting.
+1. The fact that that's where things freeze up is a red herring.
if you really didn't change anything about your zope installation, I have to wonder what else could have changed on your system... What OS are you running on? (be specific.) It wouldn't happen to be a semi-recent version of RedHat Linux, would it?
--
Paul Winkler http://www.slinkp.com _______________________________________________ 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 Thu, Jul 08, 2004 at 01:10:34PM -0400, Dan Gaibel wrote:
We're running on RedHat 7.3, Zope 2.5.1 with Python 2.1.3.
The only change I can think of was that we created a "zope" user to install the instance. It looks like the zope user had been removed. Creating a new zope user seemed to fix the problem. Does this make any sense?
maybe, it could have been a permission problem but I'd expect some error message like "Permission denied." The reason I mentioned RH is that I could imagine problems if you were using an older RedHat and upgraded glibc and ran into the oft-reported NPTL problems (google for LD_ASSUME_KERNEL for more info). Just a guess. SOunds like that wasn't relevant.
We've switched to the backup server, and we're calling the problem an "opportunity" to upgrade to 2.7.1. Hopefully we won't run into an entirely new set of problems with that.
If you have a bunch of third-party products, I would take some time to be sure that they all still work with 2.7.x. E.g. when I moved from zope 2.6.2 to 2.7.0, I had to upgrade LocalFS to localfs-1.2-andreas. I forget if there were other upgrades. And due to the many changes in configuration and installation, I found it to be a more involved upgraded than e.g. 2.5 to 2.6. Definitely worth it though, I love 2.7. -- Paul Winkler http://www.slinkp.com
participants (4)
-
Dan Gaibel -
Dennis Allison -
Jens Vagelpohl -
Paul Winkler