Re: [Zope] Zope 2.7.2 with Ape 1.0 installed in root, fails to restart, without any usefull logging, after adding a local role
Thanks, for the hint, Dieter. Unfortunately, I believe this doesn't apply in our case, as we have that set to the default (on). Tim Dieter Maurer wrote: Tim Connor wrote at 2005-6-5 18:56 -0600: I also get this error a lot when trying to add an object through the ZMI in an Apeified folder: * Module ZPublisher.Publish, line 92, in publish * Module ZPublisher.BaseRequest, line 302, in traverse * Module App.FactoryDispatcher, line 29, in __bobo_traverse__ * Module App.Product, line 67, in _product AttributeError: OFSP A colleague recently got this error because he had "enable-product-installation off" active in his configuration file. ___ 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 )
Re: [Zope] Zope 2.7.2 with Ape 1.0 installed in root, fails to restart, without any usefull logging, after adding a local role
Tim Connor wrote at 2005-6-5 18:56 -0600: >I also get this error a lot when trying to add an object through the ZMI >in an Apeified folder: > >* Module ZPublisher.Publish, line 92, in publish >* Module ZPublisher.BaseRequest, line 302, in traverse >* Module App.FactoryDispatcher, line 29, in __bobo_traverse__ >* Module App.Product, line 67, in _product > >AttributeError: OFSP A colleague recently got this error because he had "enable-product-installation off" active in his configuration file. -- Dieter ___ 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 )
Re: [Zope] Zope 2.7.2 with Ape 1.0 installed in root, fails to restart, without any usefull logging, after adding a local role
I also get this error a lot when trying to add an object through the ZMI in an Apeified folder: * Module ZPublisher.Publish, line 92, in publish * Module ZPublisher.BaseRequest, line 302, in traverse * Module App.FactoryDispatcher, line 29, in __bobo_traverse__ * Module App.Product, line 67, in _product AttributeError: OFSP Sometimes I can clear it out by trying to add a different type of object. Is that likely just a 2.7 Ape issue, as well? Thanks, Tim Shane Hathaway wrote: Tim Connor wrote: Thanks, Shane. That fixes the problem of Zope not starting, and better than the other syntax I tried, but it still doesn't fix the core problem. My root Ape installs have issues with adding a local role, as then the default roles get axed. If you add this fix then Zope re-adds Owner (and Authenticated, as you need to duplicate the fix a couple lines lower) during the start-up, but not Manager - and they are not really added, but sort of hacked in by the start-up code. Shouldn't Ape be somehow dealing with this exact situation anyways, or is there just something wrong with my installs? I'll look at it. Ape hasn't been tested with the most recent versions of Zope 2.7. Shane ___ 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 )
Re: [Zope] Zope 2.7.2 with Ape 1.0 installed in root, fails to restart, without any usefull logging, after adding a local role
Cool. Good luck. Let me know if you need a tester. ;) Tim Shane Hathaway wrote: Tim Connor wrote: Thanks, Shane. That fixes the problem of Zope not starting, and better than the other syntax I tried, but it still doesn't fix the core problem. My root Ape installs have issues with adding a local role, as then the default roles get axed. If you add this fix then Zope re-adds Owner (and Authenticated, as you need to duplicate the fix a couple lines lower) during the start-up, but not Manager - and they are not really added, but sort of hacked in by the start-up code. Shouldn't Ape be somehow dealing with this exact situation anyways, or is there just something wrong with my installs? I'll look at it. Ape hasn't been tested with the most recent versions of Zope 2.7. Shane ___ 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 )
Re: [Zope] Zope 2.7.2 with Ape 1.0 installed in root, fails to restart, without any usefull logging, after adding a local role
Thanks, Shane. That fixes the problem of Zope not starting, and better than the other syntax I tried, but it still doesn't fix the core problem. My root Ape installs have issues with adding a local role, as then the default roles get axed. If you add this fix then Zope re-adds Owner (and Authenticated, as you need to duplicate the fix a couple lines lower) during the start-up, but not Manager - and they are not really added, but sort of hacked in by the start-up code. Shouldn't Ape be somehow dealing with this exact situation anyways, or is there just something wrong with my installs? Thanks again for the help, Tim Shane Hathaway wrote: Tim Connor wrote: * Since the traceback isn't in this set of replies, heres the pertinent code: File "/usr/lib/zope-2.7.2/lib/python/OFS/Application.py", line 457, in install_required_roles app.__ac_roles__=app.__ac_roles__ + ('Owner',) TypeError: can only concatenate list (not "tuple") to list I think a quick fix is to make the above line read: app.__ac_roles__ = tuple(app.__ac_roles__) + ('Owner',) To really fix this, Ape needs to be more careful to set __ac_roles__ as tuples. Shane ___ 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 )
Re: [Zope] Zope 2.7.2 with Ape 1.0 installed in root, fails to restart, without any usefull logging, after adding a local role
I spoke too soon. I don't think it's Zope error on that type mismatch (or if it is one, it's not that one I thought). It still happens if there are multiple roles defined. As long as it hits the code adding the non-existing Owner role* the start-up croaks. So either something about Ape is causing the type mis-match or the Zope code has a bug and just usually doesn't hit that branch (which is possible, as I suspect most people don't manage to delete the Owner user). I don't know python, very well, so I don't have much of an idea. I tried changing the syntax on the ('Owner',) a couple different ways to get around the type mis-match, and then I got things started, but without any of the default users. Now it seems even more like there is an Ape bug involved (or at least a bug in getting it working on the root). Whenever I save the security tab on the root folder, it rewrites the .properties file, without the default roles defined, which puts Zope in an unstartable place. But then if I tweak Zope to make it start the default roles aren't defined. It seems I need to explicitly define those roles in the root .properties, but even if I do that manually then I can never touch the security tab (not sure if changing any other property on root causes the same problem). Tim * Since the traceback isn't in this set of replies, heres the pertinent code: File "/usr/lib/zope-2.7.2/lib/python/OFS/Application.py", line 457, in install_required_roles app.__ac_roles__=app.__ac_roles__ + ('Owner',) TypeError: can only concatenate list (not "tuple") to list Tim Connor wrote: Thanks Dennis, Between your and Shane's reply, I got it fixed: I just raised an error with the value of app.__ac_roles__, at that point in lib/python/OFS/Application.py and determined that ONLY the role I had added was being created. So going in and manually adding those starting default roles to the .properties file fixed it (running it from the console 2 days ago sure would have saved me some sleep :/). I have no idea if that is a problem with how I moved an existing project into a root install of Ape, or if it is a more generic one, but on my set-up Ape definitely only puts things in that [security] section of the .properties files when you make a change. (For example, just hitting save on the Security tab adds all those per role settings, but not the roles themselves). On everything aside from root that works better, but obviously if you ever get to the point I was at where there is only one role defined on start-up, it kill Zope, badly. Technically that might be a Zope error also - if there is only one role, it hits a type mismatch. But people shouldn't ever be getting there anyways, I suppose. Tim Dennis Allison wrote: Tim, You may want to run Zope in debug mode-- bin/runzope should do it. Also, be sure you have the event.log configured and enable.-d On Wed, 25 May 2005, Tim Connor wrote: I sent roughly this email directly to Shane Hathaway, since I hadn't asked for any help on Zope, yet, so didn't know where to look. Maybe this was a better avenue? If you read this list, Shane (or Mr. Hathaway, if you prefer), respond on whichever seems more appropriate, I guess. I don't know, let me know if I'm missing some etiquette point. Anyways, I'm using Ape 1.0 set-up in the root of Zope 2.7.2 install, based on the example fs config, and that is working fine. I was having a problem where some change was making that Zope instance not even get far enough in booting to write to the event.log (set to level all). I narrowed it down to adding a local role on the security tab of the root object. I revert the .properties file and restart - it works. I make the change again and restart - it doesn't. I diff the file, and the only difference is the define-role line. The problem is I have no idea where to start even, since no errors are thrown where I know to find them. Zope just doesn't respond at all when I try to restart it, and writes nothing to the log. If anyone could tell me what I can do to at least track down the problem, if not fix it, it would be much appreciated. Thanks, Tim ___ 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 ) ___ 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 ) ___ 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/li
Re: [Zope] Zope 2.7.2 with Ape 1.0 installed in root, fails to restart, without any usefull logging, after adding a local role
Thanks Dennis, Between your and Shane's reply, I got it fixed: I just raised an error with the value of app.__ac_roles__, at that point in lib/python/OFS/Application.py and determined that ONLY the role I had added was being created. So going in and manually adding those starting default roles to the .properties file fixed it (running it from the console 2 days ago sure would have saved me some sleep :/). I have no idea if that is a problem with how I moved an existing project into a root install of Ape, or if it is a more generic one, but on my set-up Ape definitely only puts things in that [security] section of the .properties files when you make a change. (For example, just hitting save on the Security tab adds all those per role settings, but not the roles themselves). On everything aside from root that works better, but obviously if you ever get to the point I was at where there is only one role defined on start-up, it kill Zope, badly. Technically that might be a Zope error also - if there is only one role, it hits a type mismatch. But people shouldn't ever be getting there anyways, I suppose. Tim Dennis Allison wrote: Tim, You may want to run Zope in debug mode-- bin/runzope should do it. Also, be sure you have the event.log configured and enable. -d On Wed, 25 May 2005, Tim Connor wrote: I sent roughly this email directly to Shane Hathaway, since I hadn't asked for any help on Zope, yet, so didn't know where to look. Maybe this was a better avenue? If you read this list, Shane (or Mr. Hathaway, if you prefer), respond on whichever seems more appropriate, I guess. I don't know, let me know if I'm missing some etiquette point. Anyways, I'm using Ape 1.0 set-up in the root of Zope 2.7.2 install, based on the example fs config, and that is working fine. I was having a problem where some change was making that Zope instance not even get far enough in booting to write to the event.log (set to level all). I narrowed it down to adding a local role on the security tab of the root object. I revert the .properties file and restart - it works. I make the change again and restart - it doesn't. I diff the file, and the only difference is the define-role line. The problem is I have no idea where to start even, since no errors are thrown where I know to find them. Zope just doesn't respond at all when I try to restart it, and writes nothing to the log. If anyone could tell me what I can do to at least track down the problem, if not fix it, it would be much appreciated. Thanks, Tim ___ 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 ) ___ 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 )
Re: [Zope] Zope 2.7.2 with Ape 1.0 installed in root, fails to restart, without any usefull logging, after adding a local role
Thanks, I feel like an idiot - running it as a daemon would explain why I wasn't getting as much feedback. I still don't quite get why it wasn't writing to the log though, since it is normally doing that fine. I've had that frustration with Zope before though - some errors seem to kill it in such a way it never touches the log file, even when set to all. Shane responded, so I'll see if it is an obvious Ape problem with roles on root, and then either follow-up here with a solution/more info, in case it helps someone else, or hoping for more help, if not. Well I'll throw the trace in here, in case anyone has any bright ideas, but not expect anybody to put to much thought in until we see what he has to say. ;) -- 2005-05-25T01:25:06 INFO(0) ZServer HTTP server started at Wed May 25 01:25:06 2005 Hostname: gibson Port: 9280 -- 2005-05-25T01:25:06 INFO(0) ZServer FTP server started at Wed May 25 01:25:06 2005 Hostname: gibson Port: 9221 -- 2005-05-25T01:25:06 INFO(0) Zope Set effective user to "zope-is" -- 2005-05-25T01:25:08 DEBUG(-200) ApeStorage create storage ApeStorage: /var/lib/zope/zope-is/spicerack/var/root/ Traceback (most recent call last): File "/usr/lib/zope-2.7.2/lib/python/Zope/Startup/run.py", line 50, in ? run() File "/usr/lib/zope-2.7.2/lib/python/Zope/Startup/run.py", line 19, in run start_zope(opts.configroot) File "/usr/lib/zope-2.7.2/lib/python/Zope/Startup/__init__.py", line 51, in start_zope starter.startZope() File "/usr/lib/zope-2.7.2/lib/python/Zope/Startup/__init__.py", line 230, in startZope Zope.startup() File "/usr/lib/zope-2.7.2/lib/python/Zope/__init__.py", line 47, in startup _startup() File "/usr/lib/zope-2.7.2/lib/python/Zope/App/startup.py", line 96, in startup OFS.Application.initialize(application) File "/usr/lib/zope-2.7.2/lib/python/OFS/Application.py", line 278, in initialize initializer.initialize() File "/usr/lib/zope-2.7.2/lib/python/OFS/Application.py", line 301, in initialize self.install_required_roles() File "/usr/lib/zope-2.7.2/lib/python/OFS/Application.py", line 457, in install_required_roles app.__ac_roles__=app.__ac_roles__ + ('Owner',) TypeError: can only concatenate list (not "tuple") to list Thanks, Tim Tim Dennis Allison wrote: Tim, You may want to run Zope in debug mode-- bin/runzope should do it. Also, be sure you have the event.log configured and enable. -d On Wed, 25 May 2005, Tim Connor wrote: I sent roughly this email directly to Shane Hathaway, since I hadn't asked for any help on Zope, yet, so didn't know where to look. Maybe this was a better avenue? If you read this list, Shane (or Mr. Hathaway, if you prefer), respond on whichever seems more appropriate, I guess. I don't know, let me know if I'm missing some etiquette point. Anyways, I'm using Ape 1.0 set-up in the root of Zope 2.7.2 install, based on the example fs config, and that is working fine. I was having a problem where some change was making that Zope instance not even get far enough in booting to write to the event.log (set to level all). I narrowed it down to adding a local role on the security tab of the root object. I revert the .properties file and restart - it works. I make the change again and restart - it doesn't. I diff the file, and the only difference is the define-role line. The problem is I have no idea where to start even, since no errors are thrown where I know to find them. Zope just doesn't respond at all when I try to restart it, and writes nothing to the log. If anyone could tell me what I can do to at least track down the problem, if not fix it, it would be much appreciated. Thanks, Tim ___ 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 ) ___ 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 )
Re: [Zope] Zope 2.7.2 with Ape 1.0 installed in root, fails to restart, without any usefull logging, after adding a local role
Tim, You may want to run Zope in debug mode-- bin/runzope should do it. Also, be sure you have the event.log configured and enable. -d On Wed, 25 May 2005, Tim Connor wrote: > I sent roughly this email directly to Shane Hathaway, since I hadn't > asked for any help on Zope, yet, so didn't know where to look. Maybe > this was a better avenue? If you read this list, Shane (or Mr. Hathaway, > if you prefer), respond on whichever seems more appropriate, I guess. I > don't know, let me know if I'm missing some etiquette point. > > Anyways, I'm using Ape 1.0 set-up in the root of Zope 2.7.2 install, > based on the example fs config, and that is working fine. I was having > a problem where some change was making that Zope instance not even get > far enough in booting to write to the event.log (set to level all). I > narrowed it down to adding a local role on the security tab of the root > object. I revert the .properties file and restart - it works. I make > the change again and restart - it doesn't. I diff the file, and the > only difference is the define-role line. The problem is I have no idea > where to start even, since no errors are thrown where I know to find > them. Zope just doesn't respond at all when I try to restart it, and > writes nothing to the log. > > If anyone could tell me what I can do to at least track down the > problem, if not fix it, it would be much appreciated. > > Thanks, > Tim > ___ > 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 ) > -- Dennis Allison * Computer Systems Laboratory * Gates 227 * Stanford University * Stanford CA 94305 * (650) 723-9213 * (650) 723-0033 fax * [EMAIL PROTECTED] * [EMAIL PROTECTED] ___ 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 )
[Zope] Zope 2.7.2 with Ape 1.0 installed in root, fails to restart, without any usefull logging, after adding a local role
I sent roughly this email directly to Shane Hathaway, since I hadn't asked for any help on Zope, yet, so didn't know where to look. Maybe this was a better avenue? If you read this list, Shane (or Mr. Hathaway, if you prefer), respond on whichever seems more appropriate, I guess. I don't know, let me know if I'm missing some etiquette point. Anyways, I'm using Ape 1.0 set-up in the root of Zope 2.7.2 install, based on the example fs config, and that is working fine. I was having a problem where some change was making that Zope instance not even get far enough in booting to write to the event.log (set to level all). I narrowed it down to adding a local role on the security tab of the root object. I revert the .properties file and restart - it works. I make the change again and restart - it doesn't. I diff the file, and the only difference is the define-role line. The problem is I have no idea where to start even, since no errors are thrown where I know to find them. Zope just doesn't respond at all when I try to restart it, and writes nothing to the log. If anyone could tell me what I can do to at least track down the problem, if not fix it, it would be much appreciated. Thanks, Tim ___ 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 )