What causes the failure
After updating with the latest CVS patches my formerly working installation now fails with an Authorisation failure. Before I didn't need a password at all; now even the manager password fails. Please ZOPE developers, can't we get some information into the trace back about what object/permission is causing this kind of failure. Zope Error Zope has encountered an error while publishing this resource. Unauthorized You are not authorized to access this resource. Username and password are not correct. Traceback (innermost last): File C:\Python\devel\Zope\lib\python\ZPublisher\Publish.py, line 224, in publish_module File C:\Python\devel\Zope\lib\python\ZPublisher\Publish.py, line 189, in publish File C:\Python\devel\Zope\lib\python\ZPublisher\Publish.py, line 161, in publish File C:\Python\devel\Zope\lib\python\ZPublisher\BaseRequest.py, line 460, in traverse File C:\Python\devel\Zope\lib\python\ZPublisher\HTTPResponse.py, line 560, in unauthorized Unauthorized: (see above) I found one problem already when I found that apparently my permissions for tiny tables had been modified somehow. In that case I could see the name of the tiny table that was being requested in the traceback. This permissions model is already far too complex; without random changes being introduced as the model is hacked. -- Robin Becker
The latest CVS doesn't seem to like tiny tables. Anybody got similar problems? Seems rather a brutal kind of error to say the super user can't own any objects. Zope Error Zope has encountered an error while publishing this resource. Error Type: SuperCannotOwn Error Value: Objects cannot be owned by the superuser ..... Traceback (innermost last): File C:\Python\devel\Zope\lib\python\ZPublisher\Publish.py, line 224, in publish_module File C:\Python\devel\Zope\lib\python\ZPublisher\Publish.py, line 189, in publish File C:\Python\devel\Zope\lib\python\Zope\__init__.py, line 221, in zpublisher_exception_hook (Object: ApplicationDefaultPermissions) File C:\Python\devel\Zope\lib\python\ZPublisher\Publish.py, line 175, in publish File C:\Python\devel\Zope\lib\python\ZPublisher\mapply.py, line 160, in mapply (Object: addItem) File C:\Python\devel\Zope\lib\python\ZPublisher\Publish.py, line 112, in call_object (Object: addItem) File C:\Python\devel\Zope\lib\python\Products\TinyTable\TinyTable.py, line 57, in addItem (Object: ApplicationDefaultPermissions) File C:\Python\devel\Zope\lib\python\OFS\ObjectManager.py, line 245, in _setObject (Object: ApplicationDefaultPermissions) File C:\Python\devel\Zope\lib\python\AccessControl\Owned.py, line 265, in manage_fixupOwnershipAfterAdd (Object: t) SuperCannotOwn: (see above) -- Robin Becker
Robin Becker wrote:
Zope Error
Zope has encountered an error while publishing this resource.
Error Type: SuperCannotOwn Error Value: Objects cannot be owned by the superuser
I just installed the 2.2a release and I get the same error when trying to import my exported site. Have you discovered a resolution? Thanks. -- Stand Fast, tjg. Timothy Grant tjg@exceptionalminds.com Chief Technology Officer www.exceptionalminds.com Red Hat Certified Engineer (503) 246-3630 Avalon Technology Group, Inc. fax (503) 246-3124
>>>>>>Linux...Because rebooting isn't normal<<<<<<<<<<<<
On Thu, 1 Jun 2000, Timothy Grant wrote:
Error Type: SuperCannotOwn Error Value: Objects cannot be owned by the superuser
I just installed the 2.2a release and I get the same error when trying to import my exported site.
You have to do the import as someone other than the superuser (ie: a manager account). The permission/ownership model has changed significantly in 2.2. Superuser should really be called 'bootstrapuser'. --RDM
"R. David Murray" wrote:
On Thu, 1 Jun 2000, Timothy Grant wrote:
Error Type: SuperCannotOwn Error Value: Objects cannot be owned by the superuser
I just installed the 2.2a release and I get the same error when trying to import my exported site.
You have to do the import as someone other than the superuser (ie: a manager account). The permission/ownership model has changed significantly in 2.2.
Superuser should really be called 'bootstrapuser'.
Thanks for the tip. That solved the first problem. Now, however, when I attempt to view one of my pages I get an authorization error. The traceback shows that it occurs on one of my Tiny Tables. The user I am logged in has has *full* rights to anything to do with Tiny Tables. Is there a conflict I am not seeing, or am I being to dense to notice something obvious? -- Stand Fast, tjg. Timothy Grant tjg@exceptionalminds.com Chief Technology Officer www.exceptionalminds.com Red Hat Certified Engineer (503) 246-3630 Avalon Technology Group, Inc. fax (503) 246-3124
>>>>>>Linux...Because rebooting isn't normal<<<<<<<<<<<<
In article <39373FD8.4E04CF16@exceptionalminds.com>, Timothy Grant <tjg@exceptionalminds.com> writes
"R. David Murray" wrote:
On Thu, 1 Jun 2000, Timothy Grant wrote:
Error Type: SuperCannotOwn Error Value: Objects cannot be owned by the superuser
I just installed the 2.2a release and I get the same error when trying to import my exported site.
You have to do the import as someone other than the superuser (ie: a manager account). The permission/ownership model has changed significantly in 2.2.
Superuser should really be called 'bootstrapuser'.
Thanks for the tip. That solved the first problem. Now, however, when I attempt to view one of my pages I get an authorization error. The traceback shows that it occurs on one of my Tiny Tables. The user I am logged in has has *full* rights to anything to do with Tiny Tables. Is there a conflict I am not seeing, or am I being to dense to notice something obvious?
I had the same problems wrt Tiny tables. A recent version of the CVS tree doesn't have this problem any longer; there was something wrong and a recent change fixed it. -- Robin Becker
On Thu, 1 Jun 2000, Timothy Grant wrote:
Thanks for the tip. That solved the first problem. Now, however, when I attempt to view one of my pages I get an authorization error. The traceback shows that it occurs on one of my Tiny Tables. The user I am logged in has has *full* rights to anything to do with Tiny Tables. Is there a conflict I am not seeing, or am I being to dense to notice something obvious?
I remember seeing something about a bug that affected Tiny Table access among other things. Search the mailing list archives for Tiny Tables and take a look at recent postings and I think you'll find it. A simple fix was posted. Isn't alpha software fun? <grin> --RDM
participants (3)
-
R. David Murray -
Robin Becker -
Timothy Grant