Hi there,
started using ZODB3 with a new project of mine and I've encountered a problem,
I couldn't find a solution for so far.
I'm adding instances of a class User to a storage (FileStorage for now). I did
this in a small test program which worked fine. But then I started to refactor
componen
I resolved that problem. The metaclass was screwing things up (opening the
storage before the class was created).
On 24.02.2010, at 22:32, Kaweh Kazemi wrote:
> Hi there,
>
> started using ZODB3 with a new project of mine and I've encountered a
> problem, I couldn't find
Hi zodb-dev,
during our latest zeopack runs, zeopack for our users storage fails giving this
error:
Traceback (most recent call last):
File
"/usr/local/lib/python2.6/dist-packages/ZODB3-3.10.3-py2.6-linux-i686.egg/ZEO/scripts/zeopack.py",
line 159, in _main
cs.pack(packt, wait=True)
Fi
able type: 'list'
Error:
Error packing storage users in ('localhost', 9100)
[INFO] 2012-01-30T13:36:18: (:::127.0.0.1:58682) disconnected
Kind regards,
Kaweh
On 30.01.2012, at 12:10, Jim Fulton wrote:
> On Mon, Jan 30, 2012 at 5:22 AM, Kaweh Kazemi wrote:
>> Hi zodb-de
On 30.01.2012, at 14:01, Martijn Pieters wrote:
> On Mon, Jan 30, 2012 at 13:41, Kaweh Kazemi wrote:
>> Unfortunately I'm not seeing anything useful, which is my problem:
>
> That's because that's not the ZEO server log output, but the output
> from zeopack. Yo
19) ('users') unlock:
transactions waiting: 4
[WARNING] 2012-01-31T08:23:11: (:::83.164.139.135:50940) ('users') queue
lock: transactions waiting: 4
[WARNING] 2012-01-31T08:23:11: (:::83.164.139.135:50977) ('users') unlock:
transactions waiting: 4
[WAR
ects from the second storage and
packed it previously.
And I'm still stuck how to continue beyond that.
PS: packing works if I disable gc, but I would rather remove the problematic
objects/transactions and get rid of old stuff to get a clean storage again.
Kind regards,
Kaweh
On 31.
Thanks Martijn,
I'll try to dump the pickle, and see what I can find out.
I'm still puzzled how this/what was pickled in the first place.
On 31.01.2012, at 14:39, Martijn Pieters wrote:
> On Tue, Jan 31, 2012 at 14:20, Kaweh Kazemi wrote:
>> I did the change and here we go:
machine (OS X 10.7, 64bit), while the original zeo server was running on
Python 2.6.6. (Debian, 32bit).
I will rerun the test on my local machine with Python 2.6 and see if I can
reproduce the problem.
Kind regards,
Kaweh
On 31.01.2012, at 14:51, Kaweh Kazemi wrote:
> Thanks Martijn,
>
Hi there,
Recap: last week I examined problems I had packing our 4GB users storage. With
Martijn's help I was able to fix zeo's exception output and write out the first
broken pickle that throws an exception. During my checks I realized that
running the pack in a Python 2.7 environment (using t
>>
>> I suspect a bug in the application (defining persistent classes in __main__)
>> is the root problem that's aggravated by the cPickle problem.
>
> The pickle's classes were defined in a normal module, I think Marius
> just aliased those to modules to __main__ and defined the classes
> there
11 matches
Mail list logo