Upgrade woes and product import problems
I'm trying to upgrade to 2.3.0b1 from 2.2.5b1... I installed the new version (according to the ZopeInstall HowTo, just to be safe), which started fine. I then shutdown Zope (2.3.0b1), moved the default var/Data.fs* files to a backup directory, then copied my old Data.fs* files over. When I tried to re-start 2.3.0b1, nothing happened. No debug message either. So I put the default Data.fs* files back in and restarted successfully. Fine, I thought, the database files aren't all that necessary. All the work I'd done on the previous version had been exported to a .zexp product export file, which were all subclassed from your run-of-the-mill ZClasses (image, file, folder, object manager, ZCatalog aware) and used DTML for all methods. No PythonMethods, no FSSessions, etc. So I put the .zexp file into the "import" folder and tried to import the product from within Zope. I got this error: Error Type: AttributeError Error Value: append Traceback (innermost last): File /usr/local/zope/2-3/lib/python/ZPublisher/Publish.py, line 222, in publish_module File /usr/local/zope/2-3/lib/python/ZPublisher/Publish.py, line 187, in publish File /usr/local/zope/2-3/lib/python/Zope/__init__.py, line 221, in zpublisher_exception_hook (Object: Traversable) File /usr/local/zope/2-3/lib/python/ZPublisher/Publish.py, line 171, in publish File /usr/local/zope/2-3/lib/python/ZPublisher/mapply.py, line 160, in mapply (Object: manage_importObject) File /usr/local/zope/2-3/lib/python/ZPublisher/Publish.py, line 112, in call_object (Object: manage_importObject) File /usr/local/zope/2-3/lib/python/OFS/ObjectManager.py, line 542, in manage_importObject (Object: Traversable) File /usr/local/zope/2-3/lib/python/ZODB/ExportImport.py, line 208, in importFile AttributeError: (see above) Here's my questions: 1. Why are my old data files screwing up Zope 2.3.0b1? 2. Why can't I import my product? Note: I also tried this with 2.2.5b1 --> 2.2.5, same errors. Any insights? Thanks, ajl
Well, I figured out a kludge from the "How to backup Zope data base?" thread and from the rc shutdown script. Turns out I needed to remove the Data.fs.*, pcgi.soc, and *.pid files -- leaving ONLY Data.fs and a few others, like the FSSession directory. That got both 2.2.5 and 2.3b1 to start up with my data. Only problem is that all instances of the ZClass I had created in my product (which I named ArticleProduct, btw) are broken in 2.3b1. The product itself appears in the Product Management menu, but even instances of ZClasses within the product are broken. Re-importing ArticleProduct.zexp does no good... I still get that "append" AttributeError (see traceback below). Is this a bug w/ 2.3b1 or am I missing something? Any help? ajl
I'm trying to upgrade to 2.3.0b1 from 2.2.5b1... I installed the new version (according to the ZopeInstall HowTo, just to be safe), which started fine. I then shutdown Zope (2.3.0b1), moved the default var/Data.fs* files to a backup directory, then copied my old Data.fs* files over. When I tried to re-start 2.3.0b1, nothing happened. No debug message either. So I put the default Data.fs* files back in and restarted successfully.
Fine, I thought, the database files aren't all that necessary. All the work I'd done on the previous version had been exported to a .zexp product export file, which were all subclassed from your run-of-the-mill ZClasses (image, file, folder, object manager, ZCatalog aware) and used DTML for all methods. No PythonMethods, no FSSessions, etc. So I put the .zexp file into the "import" folder and tried to import the product from within Zope. I got this error:
Error Type: AttributeError Error Value: append
Traceback (innermost last): File /usr/local/zope/2-3/lib/python/ZPublisher/Publish.py, line 222, in publish_module File /usr/local/zope/2-3/lib/python/ZPublisher/Publish.py, line 187, in publish File /usr/local/zope/2-3/lib/python/Zope/__init__.py, line 221, in zpublisher_exception_hook (Object: Traversable) File /usr/local/zope/2-3/lib/python/ZPublisher/Publish.py, line 171, in publish File /usr/local/zope/2-3/lib/python/ZPublisher/mapply.py, line 160, in mapply (Object: manage_importObject) File /usr/local/zope/2-3/lib/python/ZPublisher/Publish.py, line 112, in call_object (Object: manage_importObject) File /usr/local/zope/2-3/lib/python/OFS/ObjectManager.py, line 542, in manage_importObject (Object: Traversable) File /usr/local/zope/2-3/lib/python/ZODB/ExportImport.py, line 208, in importFile AttributeError: (see above)
Here's my questions: 1. Why are my old data files screwing up Zope 2.3.0b1? 2. Why can't I import my product?
Note: I also tried this with 2.2.5b1 --> 2.2.5, same errors.
Any insights? Thanks, ajl
That got both 2.2.5 and 2.3b1 to start up with my data. Only problem is that all instances of the ZClass I had created in my product (which I named ArticleProduct, btw) are broken in 2.3b1. The product itself appears in the Product Management menu, but even instances of ZClasses within the product are broken. Re-importing ArticleProduct.zexp does no good... I still get that "append" AttributeError (see traceback below). Is this a bug w/ 2.3b1 or am I missing something?
This sounds like a bug that pre-dates 2.3 - have you tried using Shanes 'ZGlobals Repair' utility? http://www.zope.org/Members/hathawsh/ZGlobalsRepair If not, can you give it a shot and let me know if it fixes the problem? If so, I'm inclined to weave a version of Shane's workaround into the core for 2.3 to mitigate this sort of problem. Thanks! Brian Lloyd brian@digicool.com Software Engineer 540.371.6909 Digital Creations www.digicool.com
It worked like a charm! Thanks for the tip! As you suggested, perhaps this sort of ZGlobals corruption checking should be built into the core... I'd also like to see some automatic garbage collection in the default stop script -- like removing the temporary data and pid files. I've modified mine to do this. Thanks again, ajl
This sounds like a bug that pre-dates 2.3 - have you tried using Shanes 'ZGlobals Repair' utility?
http://www.zope.org/Members/hathawsh/ZGlobalsRepair
If not, can you give it a shot and let me know if it fixes the problem? If so, I'm inclined to weave a version of Shane's workaround into the core for 2.3 to mitigate this sort of problem.
As you suggested, perhaps this sort of ZGlobals corruption checking should be built into the core...
FYI - as of beta 2, Zope will inspect the global registry for problems and rebuild it if necessary on application startup. This should remove the need to have to get the ZGlobalsRepair utility and run it manually. Brian Lloyd brian@digicool.com Software Engineer 540.371.6909 Digital Creations www.digicool.com
Hi We were asked to install a Zope server over Windows NT. Problem is - the users registered on the NT network (classic domain, not Active Directory) must be able to authenticate on the Zope server. I came across a couple products (jcNTUserFolder, NTUserFolder and smb User Folder) to do that and would like some opinions on them. Any experiences?
On Tuesday 20 February 2001 16:32, you wrote:
Hi
We were asked to install a Zope server over Windows NT. Problem is - the users registered on the NT network (classic domain, not Active Directory) must be able to authenticate on the Zope server.
I came across a couple products (jcNTUserFolder, NTUserFolder and smb User Folder) to do that and would like some opinions on them. Any experiences?
Well, there *is* one thing I'd like to mention: Authenticating against NT is basically the same as authenticating against a UNIX password file. The Apache docs warn against it for a good reason: The HTTP password travels the net unencrypted. This means, your NT domain user passwords are traveling through your Intranet or even the Internet in the clear. If you want to do it, I'd strongly suggest putting your Zope behind Apache with SSL, and prohibiting direct (HTTP, not HTTPS) access. Just my $0.02. Jan
participants (4)
-
Aaron Louie -
Brian Lloyd -
Jan Haul -
Ricardo Bánffy