Re: [Zope] Zope in Virtual Host on ISP
On 2/2/99 9:45 PM , Jeff Bauer jbauer@rubic.com said:
Yes, the two versions of Python on the system are a main symptom, though not necessarily the direct cause of your problem. Was this a source or binary install of Zope/Python?
It was a source install. Actually, I seem to have taken a step, um, forward or to the side or something. I got suspicious about the behavior I was seeing, so I took another look at my .login and .cshrc files, and sure enough, the paths were messed up ('setenv $PATH=/--deleted-path--/local/bin'. Note that '$PATH' and '=' can do interesting things to your environment.) After fixing this little gem, I deleted everything and started over. Now I'm getting the following when I execute Zope.cgi from the command line (NOTE: The '--deleted-path--' is my own editing after the fact: atlantis:/--deleted-path--/local/Zope-1.9.0-src% Zope.cgi Status: 500 Internal Error Bobo-Exception-File: /--deleted-path--/local/Zope-1.9.0-src/lib/python/ZPublisher/Request.py Content-Type: text/html Bobo-Exception-Type: exceptions.KeyError Bobo-Exception-Value: SCRIPT_NAME Content-Length: 471 Bobo-Exception-Line: 175 <html> <head> <title>exceptions.KeyError</title> </head> <body> Sorry, an error occurred.<p> <!-- Traceback (innermost last): File /--deleted-path--/local/Zope-1.9.0-src/lib/python/ZPublisher/Publish.py, line 874, in publish_module File /--deleted-path--/local/Zope-1.9.0-src/lib/python/ZPublisher/Publish.py, line 248, in __init__ File /--deleted-path--/local/Zope-1.9.0-src/lib/python/ZPublisher/Request.py, line 175, in __init__ KeyError: SCRIPT_NAME --> </body>
If you're getting the error below from the command line, you've got an issue that needs addressing before we can use Zope.cgi to override your environment with any effect.
Built-in exception class not found: EnvironmentError. Library mismatch? Warning! Falling back to string-based exceptions
Let's fix this issue first, then proceed to other tasks. I'm going to CC this to support@zope.org, because 1) They might provide information that I'm unaware of, and; 2) discover something useful (even if it's a limitation) about running Zope on ISP user accounts.
So, now it looks like one major headache is somewhat relieved. Now, about this 'exceptions.KeyError'/SCRIPT_NAME'... <grin>
Chris Larson wrote: | After fixing this little gem, I deleted everything and started over. Now | I'm getting the following when I execute Zope.cgi from the command line | (NOTE: The '--deleted-path--' is my own editing after the fact: | | <html> | <head> | <title>exceptions.KeyError</title> | </head> | -- [SNIP] -- | line 175, in __init__ | KeyError: SCRIPT_NAME The key error on SCRIPT_NAME is to be expected if you run Zope from the command line. Your web server is providing SCRIPT_NAME as a cgi variable, which ZPublisher expects to use. I'm sure you're aware that fixing things in your .login/.cshrc files will make it easier to run some tests, but has no effect on how the web server views your environment. This will only be determined by the Apache directives and overridden by directives in Zope.cgi. Regards, Jeff Bauer Rubicon, Inc.
participants (2)
-
Chris Larson -
Jeff Bauer