[Zope] ZEO manageUndo not working - DisconnectedError

Sebastian Tänzer st at taenzer.me
Wed May 6 12:38:24 CEST 2015

After more „research“ I see that the ZMS3 pip packages uses completely different versions that don’t seem to be compatible with ZEO (at least Undo is not working). I’m aware „undo“ is not a really used feature at all as revisions most of the time are beeing implemented by products. My only fear is that we’re running into other problems with the ZODB if the base setup is using wrong versions and I’d like to avoid that.


zope2 via pip uses Aquisition 2.13.8
zope2 via ZMS3 installed via pip uses Aquisition 4.1

zope2 via pip uses ZopeUndo 2.12.0
zope2 via ZMS3 installed via pip uses ZopeUndo 4.0

Most packages with ZMS3 install are newer versions.

So, basic question: What is the recommended way to setup Zope2 with ZEO. Which versions work? It seems almost impossible to understand what versions should be used. The Zope2 egg uses way older versions. Any problems with that? Which packages are safe to update?

Also, there were some patches by the ZMS people last year (https://github.com/zopefoundation/Zope/pull/13) - but Zope2 installed via pip works just fine here.
Using newer package versions require the patches though.

What is the „best“ setup if I’m using ZEO to connect with Zope2 ZEO clients AND from other remote setups (non Zope-Clients, Python command line code working with the ZODB via ClientStorage).

Maybe Tres could give me some insight on this?


> Am 06.05.2015 um 07:42 schrieb Niels Dettenbach (Syndicat IT & Internet) <nd at syndicat.com>:
> Am 6. Mai 2015 01:24:50 MESZ, schrieb "Sebastian Tänzer" <st at taenzer.me>:
>> 2015-05-06 01:16:46 WARNING ZEO.zrpc (19205) CW: error connecting to
>> ('::1', 9999): ECONNREFUSED
>> 2015-05-06 01:16:46 INFO ZEO.ClientStorage zeostorage Testing
>> connection <ManagedClientConnection ('', 9999)>
>> 2015-05-06 01:16:46 INFO ZEO.zrpc.Connection('C') (
> hmm,
> just a small shot in the dark: Even if this "should" work too - why the client tries to connect the IPv4 address of loopback and the error gives the IPv6 of it back?
> I would try to eleminate this if possible and bring Zope down to IPv4 completely, because there are still many software libraries and applications around (even some underlying os parts) which are not well tested with IPv6.
> If this solves your prob - no idea...
> hth a bit.
> cheerioh,
> Niels.
> -- 
> Niels Dettenbach
> Syndicat IT & Internet
> http://www.syndicat.com

More information about the Zope mailing list