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:
>
> Right, that's
On Tue, Jan 31, 2012 at 14:20, Kaweh Kazemi wrote:
> I did the change and here we go:
Right, that's a ZEO bug report right there then; my change should go
into ZEO trunk. Jim, did you catch it?
> I have one assumption - seeing this traceback - but I can't prove if it's
> correct: one "old" obje
I did the change and here we go:
[INFO] 2012-01-31T12:47:22: (:::127.0.0.1:36857)
pack(time=1328010442.395493) started...
[ERROR] 2012-01-31T14:06:53: (32702) Error raised in delayed method
Traceback (most recent call last):
File
"/usr/local/lib/python2.6/dist-packages/ZODB3-3.10.3-py2.6-l
On Tue, Jan 31, 2012 at 12:23, Kaweh Kazemi wrote:
> [ERROR] 2012-01-31T09:20:25: (22455) Error raised in delayed method
> None
Ugh, a quick look at the code reveals that this must've been raised by
a SlowMethodThread handler, and it indeed doesn't provide the
exception info in the log because th
Yes, I did that, unfortunately without avail. I don't get more than a None (see
below).
Our ZEO configuration inludes this:
path logs/zeo.log
format [%(levelname)s] %(asctime)s: %(message)s
Do I miss something in the eventlog section that pre
