Server Spontaneously Quitting
I have a Zope instance running on my OpenBSD machine (Zope 2.6.1 (OpenBSD package zope-2.6.1) , python 2.1.3, openbsd3) and it has been spontaneously quitting on an irregular but fairly frequent basis -- usually a couple of times per week. This is obviously unsatisfactory. Does anyone have suggestions for improving reliability -- either detecting that the server has gone down and restarting it, or (ideally) having it not crap out in the first place? I am not running behind Apache, I am running ZServer directly out. Consequently I start the process as root to bind to port 80 and it switches to the zope user in the start script. Might this be the issue? (I have tried many times to get Apache as the front end server, but apparently I am far too dense to figure it out despite all of the HOWTOs I've read.) TIA, Murray
Would you like to run Zope behind Apache? Right now, I've a lot of first hand experience getting Apache and Zope to play nice and I'd be happy to help. Sadly I have nothing to offer in terms of zope quitting though :-( Best regards, Patrick Kirk Mobile: 07876 560 646 Murray Pearson wrote:
I have a Zope instance running on my OpenBSD machine (Zope 2.6.1 (OpenBSD package zope-2.6.1) , python 2.1.3, openbsd3) and it has been spontaneously quitting on an irregular but fairly frequent basis -- usually a couple of times per week.
This is obviously unsatisfactory. Does anyone have suggestions for improving reliability -- either detecting that the server has gone down and restarting it, or (ideally) having it not crap out in the first place?
I am not running behind Apache, I am running ZServer directly out. Consequently I start the process as root to bind to port 80 and it switches to the zope user in the start script. Might this be the issue? (I have tried many times to get Apache as the front end server, but apparently I am far too dense to figure it out despite all of the HOWTOs I've read.)
TIA, Murray
_______________________________________________ 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 am not running behind Apache, I am running ZServer directly out.
When we first started out we ran an unprotected Zope server and it crashed daily. Since we put it behind Apache it's been nearly 2 years without a single crash. The problem is that Zserver falls over when it gets certain malformed requests - and there are plenty of script kids out there sending vast numbers of dodgy requests to every machine they can get. A
Murray Pearson <zope@ahadesign.ca> on 2/29/04 wrote:
This is obviously unsatisfactory. Does anyone have suggestions for improving reliability -- either detecting that the server has gone down and restarting it, or (ideally) having it not crap out in the first place?
run it under daemontools so it restarts each time it dies.
Thanks for all the tips, guys! I will get the Apache front end happening next week, and yes, Patrick, I will gratefully accept your assistance with the setup. I love the open source community! :^D Cheers, Murray
Hi Murray, I've never used OpenBSD but when installing from Ports can you specify that Apache be compiled with mod_proxy and mod_rewrite support? That's the first essential. If you like to compile from source, I've a Configuration.tmpl that has the essential edits done attached but obviously it makes more sense to edit your own copy to your own satisfaction. To see if Apache's already got that support simply enter the command 'httpd -l' at the command line. Once you are sure that both mod_rewrite and mod_proxy support are present, its really very easy to configure httpd.conf and Zope but let us know when you've verified getting to that stage. Best regards, Patrick Kirk Mobile: 07876 560 646 Murray Pearson wrote:
Thanks for all the tips, guys! I will get the Apache front end happening next week, and yes, Patrick, I will gratefully accept your assistance with the setup.
I love the open source community! :^D
Cheers, Murray
_______________________________________________ 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 )
Murray Pearson wrote at 2004-2-29 09:35 -0700:
I have a Zope instance running on my OpenBSD machine (Zope 2.6.1 (OpenBSD package zope-2.6.1) , python 2.1.3, openbsd3) and it has been spontaneously quitting on an irregular but fairly frequent basis -- usually a couple of times per week.
Do you have a Python with increased C runtime stack size? A too small stack size for Python threads is a standard problem on BSD systems. The processes die with a SIGSEGV (activate Zope logging!) when the stack overflows. -- Dieter
I'm trying to figure out where the failing is for the Apache server config. What exactly is meant by the Bad Gateway error? In what way is Zope's response invalid? Is there some place I can look to get a more detailed traceback-type error report? Some possible clues: [Thu Mar 04 13:30:50 2004] [warn] _default_ VirtualHost overlap on port 80, the first has precedence This line spits out several times when Apache starts and also after apachectl configtest. I noticed in the Zope Book that Apache 2 needs the proxy_http module so I added that as well (statically compiled it in). I still have the simple virtual hosts inside the Virtual Host Monster. Will that be confusing the issue? Shall I delete the mappings? (I'll try that next.) ....Nope, that didn't fix it either.
participants (6)
-
Andrew Veitch -
Dieter Maurer -
george donnelly -
Murray Pearson -
Murray Pearson -
Patrick Kirk