Zopistas I have intalled the Generic User Folder on Zope-2.1.0. Upon restarting and trying to access the management screen I get an IOError: Permission denied. (full traceback included in bottom) I entered Zope directly through python and deleted the GUF product from the control panel (as well as from the filesystem) but I still get the same error. I have also undone all the relevant transactions directly from python but the error persists. IMHO installing a new product should not under *any* circumstances corrupt your db. Any ideas how to restore the ZODB back to normal? Pavlos ----traceback--- : <H2>Zope Error</H2> <P>Zope has encountered an error while publishing this resource. </P> <P><STRONG>IOError</STRONG></P> Sorry, a Zope error occurred.<p> <!-- Traceback (innermost last): File /usr/local/Zope-2.1.0-src/lib/python/ZPublisher/Publish.py, line 214, in publish_module File /usr/local/Zope-2.1.0-src/lib/python/ZPublisher/Publish.py, line 179, in publish File /usr/local/Zope-2.1.0-src/lib/python/Zope/__init__.py, line 202, in zpublisher_exception_hook (Object: ApplicationDefaultPermissions) File /usr/local/Zope-2.1.0-src/lib/python/ZPublisher/Publish.py, line 165, in publish File /usr/local/Zope-2.1.0-src/lib/python/ZPublisher/mapply.py, line 160, in mapply (Object: manage) File /usr/local/Zope-2.1.0-src/lib/python/ZPublisher/Publish.py, line 102, in call_object (Object: manage) File /usr/local/Zope-2.1.0-src/lib/python/App/special_dtml.py, line 120, in __call__ (Object: manage) File /usr/local/Zope-2.1.0-src/lib/python/DocumentTemplate/DT_String.py, line 443, in __call__ (Object: manage) File /usr/local/Zope-2.1.0-src/lib/python/DocumentTemplate/DT_String.py, line 381, in cook (Object: manage) File /usr/local/Zope-2.1.0-src/lib/python/DocumentTemplate/DT_String.py, line 374, in read (Object: manage) File /usr/local/Zope-2.1.0-src/lib/python/DocumentTemplate/DT_String.py, line 538, in read_raw (Object: manage) IOError: [Errno 13] Permission denied: '/usr/local/Zope-2.1.0-src/lib/python/App/manage.dtml'
Just looking at the traceback, this doesn't appear to have anything to do with the ZODB. It looks like GUF (or something else) has either replaced or changed the permissions on App/manage.dtml so that Zope's user (nobody, probably) can't read it. ----- Original Message ----- From: Pavlos Christoforou <pavlos@gaaros.msrc.sunysb.edu>
I have intalled the Generic User Folder on Zope-2.1.0. Upon restarting and trying to access the management screen I get an IOError: Permission denied. (full traceback included in bottom)
Cheers, Evan @ 4-am
On Mon, 6 Dec 1999, Evan Simpson wrote:
Just looking at the traceback, this doesn't appear to have anything to do with the ZODB. It looks like GUF (or something else) has either replaced or changed the permissions on App/manage.dtml so that Zope's user (nobody, probably) can't read it.
That's what's puzzling. I am loged on as superuser but in anycase what ever GUF changed should have been undone when I undid the transactions. I have even truncated the Data.fs to a point way before I intalled GUF, but still I get the same error. Puzzled Pavlos
First, understand that Zope refuses to run as superuser. Since you are logged on as superuser, when you run Zope it will change its effective userid to 'nobody' (by default). Second, App/manage.dtml *isn't in Data.fs*, so transactions don't affect it. You need to look in your filesystem, under the Zope installation directory, in 'lib/python/App/'. Check the ownership and permissions on file 'manage.dtml', and make sure user 'nobody' can read it. Cheers, Evan @ 4-am ----- Original Message ----- From: Pavlos Christoforou <pavlos@gaaros.msrc.sunysb.edu>
On Mon, 6 Dec 1999, Evan Simpson wrote:
Just looking at the traceback, this doesn't appear to have anything to do with the ZODB. It looks like GUF (or something else) has either replaced or changed the permissions on App/manage.dtml so that Zope's user (nobody, probably) can't read it.
That's what's puzzling. I am loged on as superuser but in anycase what ever GUF changed should have been undone when I undid the transactions. I have even truncated the Data.fs to a point way before I intalled GUF, but still I get the same error.
On Mon, 6 Dec 1999, Evan Simpson wrote:
First, understand that Zope refuses to run as superuser. Since you are logged on as superuser, when you run Zope it will change its effective userid to 'nobody' (by default).
Evan - Superuser in the context of Zope refers to the user which is defined in the access file as opposed to a manager defined in an acl_users folder. (In any case what you say above is not true. Zope will *not* refuse to run as super-user, (check the source code of z2.py) but it will *try* to setuid to nobody (by default) if start as root)
Second, App/manage.dtml *isn't in Data.fs*, so transactions don't affect it.
True. Given though that the filesystem permissions of manage.dtml are correct I thought that installing GUF affected user permissions defined *inside* Zope (and thus in ZODB) so manage.dtml was inaccessible. Possible but not correct either because it wouldn't raise an IOError. Cheers Pavlos
From: Pavlos Christoforou <pavlos@gaaros.msrc.sunysb.edu>
Superuser in the context of Zope refers to the user which is defined in the access file as opposed to a manager defined in an acl_users folder. (In any case what you say above is not true. Zope will *not* refuse to run as super-user, (check the source code of z2.py) but it will *try* to setuid to nobody (by default) if start as root)
Sorry, didn't realize you meant it that way.
Second, App/manage.dtml *isn't in Data.fs*, so transactions don't affect it.
True. Given though that the filesystem permissions of manage.dtml are correct I thought that installing GUF affected user permissions defined *inside* Zope (and thus in ZODB) so manage.dtml was inaccessible. Possible but not correct either because it wouldn't raise an IOError.
Hmm. Check owner/permissions on 'lib' and 'python' too. Installing GUF as root *will* mess those up (and 'Products', too). Other than that, I have no ideas. Cheers, Evan @ 4-am
On Mon, 6 Dec 1999, Evan Simpson wrote:
Hmm. Check owner/permissions on 'lib' and 'python' too. Installing GUF as root *will* mess those up (and 'Products', too).
Ooooh you are right! I did a chmod -R a+r in the top folder but installing GUF as root has modified the execute bit of the directories too! Thanks Pavlos
participants (2)
-
Evan Simpson -
Pavlos Christoforou