Please keep discussion on the list. Now then, let's look at your log: On Mon, Jun 27, 2005 at 01:09:29PM -0500, Tim Suter wrote:
Traceback (most recent call last): File "/opt/zope/lib/python/OFS/Application.py", line 254, in checkGlobalRegistry keys=list(self._p_jar.root()['ZGlobals'].keys()) File "/opt/zope/lib/python/OFS/Uninstalled.py", line 46, in __getattr__ raise AttributeError, escape(name) AttributeError: keys
I've never seen that one and don't know exactly what it means, except that it's apparently related to a Product not being installed correctly. The next batch is easier:
------ 2005-06-27T13:06:44 INFO Zope Beginning attempt to rebuild the global ZClass registry. ------ 2005-06-27T13:06:44 INFO Zope The global ZClass registry has successfully been rebuilt. ------ 2005-06-27T13:06:44 INFO Zope Ready to handle requests ------ 2005-06-27T13:06:58 WARNING ZODB Could not import class 'LDAPDelegate' from module 'Products.LDAPUserFolder.LDAPDelegate' ------ 2005-06-27T13:06:58 WARNING ZODB Could not import class 'SimpleCache' from module 'Products.LDAPUserFolder.SimpleCache' ------ 2005-06-27T13:06:58 WARNING ZODB Could not import class 'LDAPUser' from module 'Products.LDAPUserFolder.LDAPUser' ------ 2005-06-27T13:06:58 WARNING ZODB Could not import class 'SimpleLog' from module 'Products.LDAPUserFolder.SimpleLog'
It's pretty clear that Zope is having a major problem with LDAPUserFolder. Possibly you have an old version of LDAPUserFolder that is not compatible with Zope 2.8? New versions can be downloaded here: http://www.dataflake.org/software/ldapuserfolder/ Or, hmmm, maybe you did not remember to install *any* of the Products that you had installed for zope 2.5? -- Paul Winkler http://www.slinkp.com
On Mon, 2005-06-27 at 16:30 -0400, Paul Winkler wrote:
Please keep discussion on the list. Now then, let's look at your log:
Yeah, that Reply to All function eludes me sometime.
__getattr__ raise AttributeError, escape(name) AttributeError: keys
I've never seen that one and don't know exactly what it means, except that it's apparently related to a Product not being installed correctly.
The next batch is easier:
------ 2005-06-27T13:06:44 INFO Zope Beginning attempt to rebuild the global ZClass registry. ------ 2005-06-27T13:06:44 INFO Zope The global ZClass registry has successfully been rebuilt. ------ 2005-06-27T13:06:44 INFO Zope Ready to handle requests ------ 2005-06-27T13:06:58 WARNING ZODB Could not import class 'LDAPDelegate' from module 'Products.LDAPUserFolder.LDAPDelegate' ------ 2005-06-27T13:06:58 WARNING ZODB Could not import class 'SimpleCache' from module 'Products.LDAPUserFolder.SimpleCache' ------ 2005-06-27T13:06:58 WARNING ZODB Could not import class 'LDAPUser' from module 'Products.LDAPUserFolder.LDAPUser' ------ 2005-06-27T13:06:58 WARNING ZODB Could not import class 'SimpleLog' from module 'Products.LDAPUserFolder.SimpleLog'
It's pretty clear that Zope is having a major problem with LDAPUserFolder. Possibly you have an old version of LDAPUserFolder that is not compatible with Zope 2.8? New versions can be downloaded here: http://www.dataflake.org/software/ldapuserfolder/
We don't want to use LDAPUserFolder for authentication. The preferred method of authentication is against an authzldap enabled apache. Or when authenticating, is it necessary to add the LDAPUserFolder? Which, this might explain why when attempting to edit the page, it would ask for authentication.
Or, hmmm, maybe you did not remember to install *any* of the Products that you had installed for zope 2.5?
That was the only product (LDAPUserFolder) that was added.
On 27 Jun 2005, at 22:27, Tim Suter wrote:
We don't want to use LDAPUserFolder for authentication. The preferred method of authentication is against an authzldap enabled apache. Or when authenticating, is it necessary to add the LDAPUserFolder? Which, this might explain why when attempting to edit the page, it would ask for authentication.
If you don't use the LDAPUserFolder then simply delete all instances in your 2.5.1-based sandbox. Just FYI, having another webserver do authentication and making that work nicely with Zope Sucks with a Capital S. Most of the time there is no valid reason to go that route, other than the lame excuse "but we only know it this way". Requests for Zope should be proxied/rewritten through and Zope can do the authentication itself. If mod_authzldap works, LDAPUserFolder will work fine as well. jens
Just FYI, having another webserver do authentication and making that work nicely with Zope Sucks with a Capital S. Most of the time there is no valid reason to go that route, other than the lame excuse "but we only know it this way".
I am sure that is why I am told to use Apache instead of LDAPUserFolder. There is very little documentation, very little, in regards to Apache authentication methods. There seems to be quite a bit of documentation in regards to LDAPUserFolder. I inherited this project of upgrading and the guy who initially set up 2.5.1 is no longer here for reference. Tim
Requests for Zope should be proxied/rewritten through and Zope can do the authentication itself. If mod_authzldap works, LDAPUserFolder will work fine as well.
jens
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
On 27 Jun 2005, at 21:30, Paul Winkler wrote:
2005-06-27T13:06:58 WARNING ZODB Could not import class 'SimpleLog' from module 'Products.LDAPUserFolder.SimpleLog'
It's pretty clear that Zope is having a major problem with LDAPUserFolder. Possibly you have an old version of LDAPUserFolder that is not compatible with Zope 2.8? New versions can be downloaded here: http://www.dataflake.org/software/ldapuserfolder/
Let's just say that whatever LDAPUserFolder version you ran with Zope 2.5.1 has long since passed into the "unsupported" pile... - Get the latest released LDAPUserFolder version and install it into your new Zope 2.8-based instance - Make a backup copy of your old ZODB - Log into a 2.5.1-based instance as the emergency user (-> see doc/ SECURITY.txt in your 2.5.1 Zope installation about how to create one) - if you don't have a LDAPUserFolder in the Zope root you can skip that and log in as a Manager user from the root user folder - Delete every single LDAPUserFolder instance you have - Stop Zope - Copy the Data.fs into your Zope 2.8-based sandbox - If you had a LDAPUserFolder at the root, make sure you're set up for an emergency user - Start Zope and log in either as an emergency user or a root user folder manager - Recreate all LDAPUserFolder instances. jens
participants (3)
-
Jens Vagelpohl -
Paul Winkler -
Tim Suter