[Zope] ZEO manageUndo not working - DisconnectedError
st at taenzer.me
Wed May 6 15:26:23 CEST 2015
After further testing I was able to sort this one out by downgrading ZopeUndo to 2.12.0 (pip install ZopeUndo==2.12.0 --force —upgrade).
PyPi only said 4.0 brought Py3 compability. Should I expect any problems using ZopeUndo 2.12 + ZEO/ZODB4/ZODB3 with their latest versions?
> 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 ('127.0.0.1', 9999)>
>> 2015-05-06 01:16:46 INFO ZEO.zrpc.Connection('C') (127.0.0.1:9999)
> 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.
> Niels Dettenbach
> Syndicat IT & Internet
More information about the Zope