On Mon, Jan 7, 2013 at 1:20 PM, Claudiu Saftoiu wrote:
>> > I'm afraid this doesn't seem to help me figure out what's wrong...
>>
>> I suspect your database is corrupted. You'd probably want to look at
>> the record in question to be sure.
>
>
> Sure, I've re-run the pack and will dump the pickle
>
> > I'm afraid this doesn't seem to help me figure out what's wrong...
>
> I suspect your database is corrupted. You'd probably want to look at
> the record in question to be sure.
>
Sure, I've re-run the pack and will dump the pickled object to a file to
inspect it - is that what you meant? (H
On Mon, Jan 7, 2013 at 1:04 PM, Claudiu Saftoiu wrote:
>
>> How do I go about fixing this? Let me know if I can provide any other
>> information that would be helpful.
>
>
> I took the advice in this thread:
> https://mail.zope.org/pipermail/zodb-dev/2012-January/014526.html
>
> The exception that
> How do I go about fixing this? Let me know if I can provide any other
> information that would be helpful.
>
I took the advice in this thread:
https://mail.zope.org/pipermail/zodb-dev/2012-January/014526.html
The exception that comes up, from the zeo server log, is:
2013-01-07T13:01:49 ERROR Z
I noticed my DB had swelled to 132 gigabytes (as of 3 days ago; it's 160
gigabytes today) and it seems to be because zeopack has started failing:
tsa@sp2772c:~/db$ /home/tsa/env/bin/zeopack -u /home/tsa/db/zeo.sock
Traceback (most recent call last):
File "/home/tsa/env/lib/python2.6/site-package
