thanks for the „shot“, yet disabling IPv6 locally on the VM does not help, same error: (server): 2015-05-06T10:05:51 INFO ZEO.StorageServer (127.0.0.1:44833) disconnected ------ 2015-05-06T10:05:51 INFO ZEO.zrpc.Connection('S') (127.0.0.1:44835) received handshake 'Z3101' ------ 2015-05-06T10:06:35 ERROR ZEO.zrpc (3040) can't decode message: '(K\x05I00\nU\x08undoInfo(K\x00K\x14}U\x0bdescriptioncco...' ------ 2015-05-06T10:06:35 ERROR ZEO.zrpc.Connection('S') (127.0.0.1:44835) Error caught in asyncore Traceback (most recent call last): File "/opt/python/2.7.9/lib/python2.7/asyncore.py", line 83, in read obj.handle_read_event() File "/opt/python/2.7.9/lib/python2.7/asyncore.py", line 449, in handle_read_event self.handle_read() File "/opt/python/zope2-latest/lib/python2.7/site-packages/ZEO/zrpc/smac.py", line 240, in handle_read self.message_input(msg) File "/opt/python/zope2-latest/lib/python2.7/site-packages/ZEO/zrpc/connection.py", line 417, in message_input msgid, async, name, args = self.decode(message) File "/opt/python/zope2-latest/lib/python2.7/site-packages/ZEO/zrpc/marshal.py", line 80, in server_decode return unpickler.load() # msgid, flags, name, args File "/opt/python/zope2-latest/lib/python2.7/site-packages/ZEO/zrpc/marshal.py", line 120, in server_find_global raise ZRPCError("import error %s: %s" % (module, msg)) ZRPCError: import error copy_reg: ------ 2015-05-06T10:06:35 INFO ZEO.StorageServer (127.0.0.1:44835) disconnected ------ 2015-05-06T10:06:35 INFO ZEO.zrpc.Connection('S') (127.0.0.1:44837) received handshake ‚Z3101' More ideas? :-)
Am 06.05.2015 um 07:42 schrieb Niels Dettenbach (Syndicat IT & Internet) <nd@syndicat.com>:
Am 6. Mai 2015 01:24:50 MESZ, schrieb "Sebastian Tänzer" <st@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) 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