gluster-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gluster-devel] lots of errors from latest TLA on HA


From: Raghavendra G
Subject: Re: [Gluster-devel] lots of errors from latest TLA on HA
Date: Mon, 12 Jan 2009 20:53:20 +0400

Hi Mickey,

what are the transeports of client and serverts ? you seem to be using different transports on client and server side? If so, can you use the same transport on both sides?

regards,
On Mon, Jan 12, 2009 at 7:42 PM, Mickey Mazarick <address@hidden> wrote:
I just updated our test cluster to the newest tla and it works fine but throws a lot of errors on the HA/AFR/unify portion over ib-verbs/tcp. The errors only happen when HA is enabled (HA is setup ibverbs<->tcp )

The client errors:
2009-01-12 10:34:44 E [saved-frames.c:148:saved_frames_unwind] brick6tcp: forced unwinding frame type(2) op(SETVOLUME)
2009-01-12 10:34:44 E [client-protocol.c:5583:client_setvolume_cbk] brick6tcp: setvolume failed (Transport endpoint is not connected)
2009-01-12 10:34:54 E [socket.c:473:__socket_proto_validate_header] brick-ns1tcp: socket header signature does not match :O (51.50.31)
2009-01-12 10:34:54 E [socket.c:588:socket_proto_state_machine] brick-ns1tcp: socket header validation failed (192.168.1.201:6997). possible mis-match of 'transport-type' in server and client volumes, or different versions of glusterfs used
2009-01-12 10:34:54 E [saved-frames.c:148:saved_frames_unwind] brick-ns1tcp: forced unwinding frame type(2) op(SETVOLUME)
2009-01-12 10:34:54 E [client-protocol.c:5583:client_setvolume_cbk] brick-ns1tcp: setvolume failed (Transport endpoint is not connected)
2009-01-12 10:34:54 E [socket.c:473:__socket_proto_validate_header] brick-ns2tcp: socket header signature does not match :O (51.50.31)
2009-01-12 10:34:54 E [socket.c:588:socket_proto_state_machine] brick-ns2tcp: socket header validation failed (192.168.1.202:6997). possibl

The server errors:
2009-01-12 10:38:16 C [ib-verbs.c:1671:ib_verbs_handshake_pollin] transport/ib-verbs: server: remote-host(192.168.1.74:993)'s transport type is different
2009-01-12 10:38:16 E [ib-verbs.c:213:__ib_verbs_disconnect] transport/ib-verbs: shutdown () - error: Transport endpoint is not connected
2009-01-12 10:38:16 E [server-protocol.c:7354:server_protocol_cleanup] server: invalid argument: cprivate
2009-01-12 10:38:18 C [ib-verbs.c:1671:ib_verbs_handshake_pollin] transport/ib-verbs: server: remote-host(127.0.0.1:1023)'s transport type is different
2009-01-12 10:38:18 E [ib-verbs.c:213:__ib_verbs_disconnect] transport/ib-verbs: shutdown () - error: Transport endpoint is not connected
2009-01-12 10:38:18 E [ib-verbs.c:1940:tcp_connect_finish] server: tcp connect to 127.0.0.1:1023 failed (Connection reset by peer)
2009-01-12 10:38:18 E [server-protocol.c:7354:server_protocol_cleanup] server: invalid argument: cprivate
2009-01-12 10:38:18 C [ib-verbs.c:1671:ib_verbs_handshake_pollin] transport/ib-verbs: server: remote-host(127.0.0.1:1023)'s transport type is different
2009-01-12 10:38:18 C [ib-verbs.c:1671:ib_verbs_handshake_pollin] transport/ib-verbs: server: remote-host(127.0.0.1:1023)'s transport type is different
2009-01-12 10:38:18 E [ib-verbs.c:213:__ib_verbs_disconnect] transport/ib-verbs: shutdown () - error: Transport endpoint is not connected

Thanks for all the great work!
--


_______________________________________________
Gluster-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/gluster-devel



--
Raghavendra G


reply via email to

[Prev in Thread] Current Thread [Next in Thread]