Re: [Zope] Server Spontaneously Quitting
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. ( My apologies if this is a double post )
Murray Pearson wrote:
What exactly is meant by the Bad Gateway error?
Apache tried to proxy a request but the other end didn't answer...
In what way is Zope's response invalid?
Zope was not alive to reply.
Is there some place I can look to get a more detailed traceback-type error report?
There isn't really much more to it, it's a glorious "connection refused" error.
Some possible clues: [Thu Mar 04 13:30:50 2004] [warn] _default_ VirtualHost overlap on port 80, the first has precedence
...yeah, might want to get to the bottom of those. #apache on irc.freenode.net is where I'd go... FWIW, Zope dying isn't usually the result of an Apache or VHM misconfiguration. I'd look at zope trying to write to a non existent stdout (ie: print statements in Zope products you've installed) or BSD issues... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
participants (2)
-
Chris Withers -
Murray Pearson