- first install, first connect
Install an compile went fine with no errors (running ZopeHttpServer on a Slackware Linux box) First connect after an easy install , I request "http://myhostnamewenthere:8080/manage" and netscape returned, "Document contains no data". My first guess was that I didn't have permissions to the dir Zope needed, but I checked and I do. So is Zope serving a broken header file? or is this a common first time error? I checked the list archive with no luck. I couldn't find a file/dir "manage" anywhere, even tried a search from "/" with no luck. DAve. The server log shows the following errors. <log> Publishing module Main Serving HTTP on port 8080 ... ---------------------------------------- Exception happened during processing of request from ('xxx.xxx.xxx.xxx, 2194) ---------------------------------------- -------------------------------------er.py", line 295, in publish_module File "/home/dad/dadstuff/Zope-1.9b1-src/ZopeHTTPServer/ZopeHTTPServer.py", line 321, in get_environment File "/usr/lib/python1.5/SimpleHTTPServer.py", line 87, in translate_path path = os.getcwd() error: (13, 'Permission denied') Traceback (innermost last): File "/home/dad/dadstuff/Zope-1.9b1-src/ZopeHTTPServer/ZopeHTTPServer.py", line 355, in handle_request File "/usr/lib/python1.5/SocketServer.py", line 239, in process_request self.finish_request(request, client_address) File "/usr/lib/python1.5/SocketServer.py", line 243, in finish_request self.RequestHandlerClass(request, client_address, self) File "/usr/lib/python1.5/SocketServer.py", line 362, in __init__ self.handle() File "/usr/lib/python1.5/BaseHTTPServer.py", line 258, in handle method() File "/home/dad/dadstuff/Zope-1.9b1-src/ZopeHTTPServer/ZopeHTTPServer.py", line 288, in do_GET File "/home/dad/dadstuff/Zope-1.9b1-src/ZopeHTTPServer/ZopeHTTPServer.py", line 295, in publish_module File "/home/dad/dadstuff/Zope-1.9b1-src/ZopeHTTPServer/ZopeHTTPServer.py", line 321, in get_environment File "/usr/lib/python1.5/SimpleHTTPServer.py", line 87, in translate_path path = os.getcwd() error: (13, 'Permission denied') </log>
Dave Goodrich wrote:
Install an compile went fine with no errors (running ZopeHttpServer on a Slackware Linux box) First connect after an easy install , I request "http://myhostnamewenthere:8080/manage" and netscape returned, "Document contains no data". My first guess was that I didn't have permissions to the dir Zope needed, but I checked and I do. So is Zope serving a broken header file?
No.
or is this a common first time error?
No.
I checked the list archive with no luck. I couldn't find a file/dir "manage" anywhere, even tried a search from "/" with no luck.
manage is a method defined in a Python class (from a DTML file defined in the source tree. I'm 99.99% sure that manage is not really the problem. See note below:
The server log shows the following errors.
How did you start the server? Were you root or an ordinary user?
<log>
Publishing module Main Serving HTTP on port 8080 ... ---------------------------------------- Exception happened during processing of request from ('xxx.xxx.xxx.xxx, 2194) ---------------------------------------- -------------------------------------er.py", line 295, in publish_module File "/home/dad/dadstuff/Zope-1.9b1-src/ZopeHTTPServer/ZopeHTTPServer.py", line 321, in get_environment File "/usr/lib/python1.5/SimpleHTTPServer.py", line 87, in translate_path path = os.getcwd() error: (13, 'Permission denied')
For some reason os.getcwd is failing. Can anyone think of a reason why os.getcwd would fail? Jim -- Jim Fulton mailto:jim@digicool.com Technical Director (888) 344-4332 Python Powered! Digital Creations http://www.digicool.com http://www.python.org Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.
Jim Fulton wrote:
Dave Goodrich wrote:
The server log shows the following errors. [...]
Publishing module Main Serving HTTP on port 8080 ... ---------------------------------------- Exception happened during processing of request from ('xxx.xxx.xxx.xxx, 2194) ---------------------------------------- -------------------------------------er.py", line 295, in publish_module File "/home/dad/dadstuff/Zope-1.9b1-src/ZopeHTTPServer/ZopeHTTPServer.py", line 321, in get_environment File "/usr/lib/python1.5/SimpleHTTPServer.py", line 87, in translate_path path = os.getcwd() error: (13, 'Permission denied')
For some reason os.getcwd is failing.
Can anyone think of a reason why os.getcwd would fail?
Sorry, I'm not running Linux on my PC at the moment. But under Solaris: ERRORS getcwd() will fail if one or more of the following are true: EACCES A parent directory cannot be read to get its name. ... -- Mitch Chapman | 4105 Executive Drive Ohio Electronic Engravers, Inc. | Beavercreek, OH 45430 mchapman@oee.com | import StandardDisclaimer
On Wed, 9 Dec 1998, Mitch Chapman wrote:
Sorry, I'm not running Linux on my PC at the moment. But under Solaris:
ERRORS getcwd() will fail if one or more of the following are true:
EACCES A parent directory cannot be read to get its name. ... That is so, because of the way getcwd() is (was orginally?) implemented: It basically works by looking recursivly on the parent directory, reading it, and comparing inode numbers.
So let's say, I'm in cwd with inum=10050, than cwd starts by reading .., and notices that ``andreas'' happens to have inum 10050, so getcwd() just learned that the last component is andreas. And it goes so one till it finds ``/''. That's why in bash, there is a difference between the cwd as displayed by bash, and say by ``sh -c pwd'', because bash tracks cd commands, which make it remember symbolic links, and the standalone pwd does the recursive thing ;) And for the recursive reading stuff you need read rights in all directories leading to the current directory, ... Andreas -- Win95: n., A huge annoying boot virus that causes random spontaneous system crashes, usually just before saving a massive project. Easily cured by UNIX. See also MS-DOS, IBM-DOS, DR-DOS, Win 3.x, Win98.
participants (4)
-
Andreas Kostyrka -
Dave Goodrich -
Jim Fulton -
Mitch Chapman