Re: [Zope] Zope Still Crashes Daily
Hi guys, OK, I got python compiled with
make OPT="-DNDEBUG -g -O3 -Wall -Wstrict-prototypes -DHAVE_THREADS -DTHREAD_STACK_SIZE=1000000"
and I compiled Zope 2.7 and I've familiarized myself with its unexpected new form. I have configured it to open with the ports shifted up 1000 to avoid conflicts with Zope 2.6 which is still running. This isn't a problem, is it? They're not even using the same Python. I also told it to listen only on the internal network address, for security. I can route that out through Apache which will completely eliminate random IIS/script-kiddie attacks on Zope..... right? Anyhow, it all seemed fine until the starting gun: -bash-2.05b$ sudo ./bin/runzope Password: Traceback (most recent call last): File "/usr/local/src/Zope-2.7.0/lib/python/Zope/Startup/run.py", line 49, in ? run() [bla bla bla] File "/usr/local/src/Zope-2.7.0/lib/python/ZODB/__init__.py", line 18, in ? import cPersistence, Persistence ImportError: No module named cPersistence So I RTFM'd, and then python setup.py build_ext -if in the Zope source directory... then -bash-2.05b$ sudo ./bin/runzope .....and Zope 2.7 is now running!!! Zope Version (Zope 2.7.0, python 2.3.3, openbsd3) Python Version 2.3.3 (#1, Mar 25 2004, 12:48:50) [GCC 2.95.3 20010125 (prerelease, propolice)] System Platform openbsd3 Thanks for your help, people! I will try migrating my stuff from the old server to the new (it's REALLY handy having both running in the meanwhile.) I'll see if this actually stabilizes it.
(oops, you slipped into html mail mode :-S) Murray Pearson wrote:
I have configured it to open with the ports shifted up 1000 to avoid conflicts with Zope 2.6 which is still running. This isn't a problem, is it?
No, that's fine...
I also told it to listen only on the internal network address, for security. I can route that out through Apache which will completely eliminate random IIS/script-kiddie attacks on Zope..... right?
Correct, although you should really firewall that box so only the port(s) Apache listens on are open to the outside world... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
hi I had random hangs of Zope 2.6.4 (python 2.1) with plone, on Linux, upgraded to zope 2.7.0 python 2.3.4 plone 2.0, in hope to solve the problem, and it instead it got to be much worse moreover the upgrade was a mess: most things that were working before were not working after (for example, the password of all users were somewhat not valid afterwards did you fare better? a. -- Andrea Mennucc "one houndred and fifty - the chicken sings"
Chris: Sorry about the HTML email *blush*! Here's the arrangement I have now: my Zope 2.6.1 is running as before, on all network interfaces. So is Apache, so from the outside it looks like nothing is different and it works as well as always (not that *that's* a lot, but I'm not downhill anyway!) Zope 2.7 is running on higher numbered ports but only on the firewalled port. Apache can see it, but nobody outside can. Great. I shut down Zope 2.6, copied its ZODB to the new Zope 2.7 instance, and restarted both Zopes. There's all my stuff in the new environment, but things like database adapters are broken (not surprisingly). Andrea: I agree, it's not easy to get the machinery working. I'm still fairly new in Python and I'm feeling a bit mystified at times. Still, I feel the shortcoming is my lack of understanding and not inherent weakness in the products! I probably will whack my thumb with the hammer a few more times but it'll make sense in the end. Meanwhile, I'm burning CDs for Fedora Linux to try that out. I also tried FreeBSD but thought "more different is better." We shall see! Murray
Murray Pearson wrote:
I shut down Zope 2.6, copied its ZODB to the new Zope 2.7 instance, and restarted both Zopes. There's all my stuff in the new environment, but things like database adapters are broken (not surprisingly).
You should start using INSTANCE_HOME, which Zope 2.7 does by default. Then you can put your products in $INSTANCE_HOME/Products and they'll stick with you when you switch Zope version ;-) "Database adapters are broken" isn't such a helpful error report either ;-) (exception type, traceback and value please!)
Meanwhile, I'm burning CDs for Fedora Linux to try that out. I also tried FreeBSD but thought "more different is better."
Go Debian! :-) Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
participants (4)
-
Chris Withers -
debdev@tonelli.sns.it -
Murray Pearson -
Murray Pearson