Hello,
I have a customer who run a ZEO setup with ZODB 3.8.4. They report
this error:
2011-01-31T12:02:24 Unexpected error
Traceback (most recent call last):
File
/opt/zope/newbuildout/parts/zope2/lib/python/ZODB/ConflictResolution.py,
line 207, in tryToResolveConflict
resolved =
On 28/01/2011 21:58, Jürgen Herrmann wrote:
Afaics you use zodbpack's default of days=0. This is known to produce
POSKeyErrors if the database is written to while packing.
Where is this documented?
Does this apply to history-keeping or history-free storages?
Try with
something
On 01/31/2011 06:02 PM, Chris Withers wrote:
On 28/01/2011 21:58, Jürgen Herrmann wrote:
Afaics you use zodbpack's default of days=0. This is known to produce
POSKeyErrors if the database is written to while packing.
Where is this documented?
It is not known to me. :-)
I'll not pack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/31/2011 07:27 AM, Sylvain Viollon wrote:
Hello,
I have a customer who run a ZEO setup with ZODB 3.8.4. They report
this error:
2011-01-31T12:02:24 Unexpected error
Traceback (most recent call last):
File
On 31/01/2011 16:30, Chris Withers wrote:
I got the following error when trying to run zodbconvert against a
clustered MySQL environment running RHCS:
File
/var/buildout-eggs/MySQL_python-1.2.3-py2.6-linux-i686.egg/MySQLdb/connections.py,
line 36, in defaulterrorhandler
raise
On 01/31/2011 06:30 PM, Chris Withers wrote:
Hi Shane,
I got the following error when trying to run zodbconvert against a
clustered MySQL environment running RHCS:
File
/var/buildout-eggs/MySQL_python-1.2.3-py2.6-linux-i686.egg/MySQLdb/connections.py,
line 36, in defaulterrorhandler
On 02/01/2011 12:19 AM, Chris Withers wrote:
Hi Shane,
This one's less serious if it is what I think it is:
Traceback (most recent call last):
File bin/zodbconvert, line 24, inmodule
relstorage.zodbconvert.main()
File
