Hi, Well, I thought the upgrade to 2.3.2b2 would solve the problem but it hasn't :-( I have a (very important :-S) Zope instance which hangs at what seems like the slightest touch. The symptoms are as follows: 1. Go to a given URL, which doesn't respond (browser sits and spins) 2. Doing a 'top' on the server shows python nowhere to be seen (so it's not infinite-loop-processor-hogging) 3. ps shows the python threads are all still there, but none of them will respond. 3. doing a ./stop sucessfully stops Zope (the broswer returns a 'reset by peer') 4. doing a ./start yields the following the the stupid log file: 2001-04-27T15:05:38 PANIC(300) z2 Startup exception Traceback (innermost last): File /usr/local/zope/Zope-2.3.2b2-src/z2.py, line 566, in ? File <string>, line 1, in ? File /usr/local/zope/Zope-2.3.2b2-src/lib/python/Zope/__init__.py, line 110, in ? File /usr/local/zope/Zope-2.3.2b2-src/lib/python/ZODB/FileStorage.py, line 264, in __init__ File /usr/local/zope/Zope-2.3.2b2-src/lib/python/ZODB/lock_file.py, line 101, in lock_file StorageSystemError: Could not lock the database file. There must be another process that has opened the file. <p> 5. The only way I can get Zope to start again is do do a: killall -9 python ...now start behaves normally and the cycle begins again (averaging around once every 10 minutes now :-( ) Can anyone suggest how I might go about tracking this down? It's really beginning to piss me off. That said, I've seen quite a few posts now complaining about Zope hanging and crashing, so I'm actually beginning to worry about using Zope from a stability point of view. Help! Chris
The symptoms are as follows: 1. Go to a given URL, which doesn't respond (browser sits and spins) 2. Doing a 'top' on the server shows python nowhere to be seen (so it's not infinite-loop-processor-hogging) 3. ps shows the python threads are all still there, but none of them will respond. 3. doing a ./stop sucessfully stops Zope (the broswer returns a 'reset by peer') 4. doing a ./start yields the following the the stupid log file:
Can anyone suggest how I might go about tracking this down? It's really beginning to piss me off. That said, I've seen quite a few posts now complaining about Zope hanging and crashing, so I'm actually beginning to worry about using Zope from a stability point of view.
These symptoms are indeed very similar to what we had on the demo.iuveno-net.de site. We had an average "up-time" of around an hour or so, and the system also didn't really crash but just "hang" ... Right now we don't face these problems any more. As far as I know, the only thing Stephan changed on the server was exchanging the CoreSession tracking by the newest version (0.8 I think), which had to be patched to run for us AFAIK. Now the server is reliable again. I was really scared by this issue, too, as we had the same problems on a demo server for a customer ... Joachim.
Joachim Werner wrote:
Right now we don't face these problems any more. As far as I know, the only thing Stephan changed on the server was exchanging the CoreSession tracking by the newest version (0.8 I think), which had to be patched to run for us AFAIK. Now the server is reliable again.
Well, CST 0.8 worked out of the box for us, but it hasn't helped the problem. (and we still get loads of those "None has no attribute load" errors ;-) cheers, Chris
On Fri, 27 Apr 2001, Chris Withers wrote:
Well, I thought the upgrade to 2.3.2b2 would solve the problem but it hasn't :-( I have a (very important :-S) Zope instance which hangs at what seems like the slightest touch.
Maybe I can help. I've seen similar behaviour, and by some chance I discovered what it was that was causing it - which might not be the same thing that is causing your problem. When, in my Zope Python Product, I call a method that does not exist, Zope dies, restarts and then is fine again. If something (another method or a browser perhaps) is calling this method again and again, Zope does a die, restart, rinse, repeat. I think the problem is that it doesn't throw the necessary Exception, or that it actually throws it, but it is somehow captured by a try-except that I've put out somewhere, so it doesn't show. The problem is fixed once I stop calling the non-existant method. I haven't had time to check whether this is the case with the latest version of Zope, but it is with Zope 2.3.1b1, at least. Maybe you have a method that is called when someone access that URL, but that method does not exist?
participants (3)
-
Chris Withers -
Erik Enge -
Joachim Werner