Re: zms update trouble

Frank Rossi <[email protected]>
Newsgroups gmane.comp.cms.zms.devel
Organization telesma medialab
Message-ID <[email protected]>
I've look more deeply in the traceback now.

> Module Products.zms._xmllib, line 666, in parse 

This is the corresponding section in _xmllib:

        #### parsing ####
        #++ if _globals.debug: print "#### parsing ####"
        if type(input)=='string':
          # input is a string!
          rv = p.Parse(input, 1)
        else:
          # input is a file object!
          while 1:
            if Globals.DatabaseVersion == '3':
              get_transaction().commit(1)           #line 666

Is it possible that the error is caused by an corrupted binary file, an 
image or pdf document ?

Frank


On Tue, 3 Feb 2009 23:34:33 +0100, Frank Rossi wrote:
> I've another more detailed traceback on import of an ZMS 2.1.2.16-xlang 
> .zexp export
> to ZMS 2.2.0-b28
> 
> Exception Type TypeError 
> Exception Value can't pickle function objects 
> 
> Traceback (innermost last): 
> 
> Module ZPublisher.Publish, line 100, in publish 
> Module ZPublisher.mapply, line 88, in mapply 
> Module ZPublisher.Publish, line 40, in call_object 
> Module App.special_dtml, line 62, in __call__ 
> Module DocumentTemplate.DT_String, line 474, in __call__ 
> Module App.special_dtml, line 62, in __call__ 
> Module DocumentTemplate.DT_String, line 474, in __call__ 
> Module App.special_dtml, line 62, in __call__ 
> Module DocumentTemplate.DT_String, line 474, in __call__ 
> Module DocumentTemplate.DT_Util, line 201, in eval
> __traceback_info__: manage_lang 
> Module <string>, line 0, in ? 
> Module Products.zms.zms, line 693, in updateVersion 
> Module Products.zms.zms, line 571, in recurse_updateVersionPatch 
> Module Products.zms._confmanager, line 73, in updateConf 
> Module Products.zms._confmanager, line 111, in importConf 
> Module Products.zms._metaobjmanager, line 93, in importXml 
> Module Products.zms._zmsglobals, line 633, in parseXmlString 
> Module Products.zms._xmllib, line 666, in parse 
> Module ZODB.Transaction, line 233, in commit 
> Module ZODB.Transaction, line 348, in _commit_objects 
> Module ZODB.Connection, line 418, in commit
> __traceback_info__: (('Products.zms._zmsattributecontainer', 
> 'ZMSAttributeContainer'), '\x00\x00\x00\x00\x00\x016>', '') 
> Module copy_reg, line 69, in _reduce_ex 
> TypeError: can't pickle function objects 
> 
> On Tue, 3 Feb 2009 19:06:25 +0100, Frank Rossi wrote:
>> Dear ZMS users,
>> 
>> im in the process of update an old ZMS site for an customer who asked 
>> me to do this for him.
>> I've already updated some own ZMS instances in the last year. From ZMS 
>> 2.7 to the current 2.11 release and it worked just fine.
>> 
>> But this one is much older now and I ran in some troubles...
>> I've deactivated all Workflow, Cache, History, Catalog.
>> 
>> Start System:
>> Zope 2.6.4, Python 2.2.3
>> ZMS 2.1.2.7 (build #117b)
>> 
>> Step 1 System:
>> Zope 2.7.4, Python 2.3.4
>> zms_21_116m32pr.tar.gz
>> ->Import successful
>> 
>> Step 2 System:
>> Zope 2.7.4, Python 2.3.4
>> ZMS-2.2.0-b28
>> -> Import failed
>> 
>> Exception traceback:
>> 
>> Exception Type TypeError 
>> Exception Value can't pickle function objects 
>> 
>> Traceback (innermost last): 
>> 
>> Module ZPublisher.Publish, line 104, in publish 
>> Module Zope.App.startup, line 221, in commit 
>> Module ZODB.Transaction, line 193, in commit 
>> Module ZODB.Transaction, line 233, in commit 
>> Module ZODB.Transaction, line 348, in _commit_objects 
>> Module ZODB.Connection, line 418, in commit
>> __traceback_info__: (('Products.zms._zmsattributecontainer', 
>> 'ZMSAttributeContainer'), '\x00\x00\x00\x00\x00\x00D\x1e', '') 
>> Module copy_reg, line 69, in _reduce_ex 
>> TypeError: can't pickle function objects 
>> 
>> Any help or suggestion is much apprectiated
>> 
>> Best!
>> Frank Rossi
>> 
>> 
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.