Hi Mickey,<br><br>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?<br><br>regards,<br><div class="gmail_quote">
On Mon, Jan 12, 2009 at 7:42 PM, Mickey Mazarick <span dir="ltr"><<a href="mailto:mic@digitaltadpole.com">mic@digitaltadpole.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
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 )<br>
<br>
The client errors:<br>
2009-01-12 10:34:44 E [saved-frames.c:148:saved_frames_unwind] brick6tcp: forced unwinding frame type(2) op(SETVOLUME)<br>
2009-01-12 10:34:44 E [client-protocol.c:5583:client_setvolume_cbk] brick6tcp: setvolume failed (Transport endpoint is not connected)<br>
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)<br>
2009-01-12 10:34:54 E [socket.c:588:socket_proto_state_machine] brick-ns1tcp: socket header validation failed (<a href="http://192.168.1.201:6997" target="_blank">192.168.1.201:6997</a>). possible mis-match of 'transport-type' in server and client volumes, or different versions of glusterfs used<br>
2009-01-12 10:34:54 E [saved-frames.c:148:saved_frames_unwind] brick-ns1tcp: forced unwinding frame type(2) op(SETVOLUME)<br>
2009-01-12 10:34:54 E [client-protocol.c:5583:client_setvolume_cbk] brick-ns1tcp: setvolume failed (Transport endpoint is not connected)<br>
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)<br>
2009-01-12 10:34:54 E [socket.c:588:socket_proto_state_machine] brick-ns2tcp: socket header validation failed (<a href="http://192.168.1.202:6997" target="_blank">192.168.1.202:6997</a>). possibl<br>
<br>
The server errors:<br>
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<br>
2009-01-12 10:38:16 E [ib-verbs.c:213:__ib_verbs_disconnect] transport/ib-verbs: shutdown () - error: Transport endpoint is not connected<br>
2009-01-12 10:38:16 E [server-protocol.c:7354:server_protocol_cleanup] server: invalid argument: cprivate<br>
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<br>
2009-01-12 10:38:18 E [ib-verbs.c:213:__ib_verbs_disconnect] transport/ib-verbs: shutdown () - error: Transport endpoint is not connected<br>
2009-01-12 10:38:18 E [ib-verbs.c:1940:tcp_connect_finish] server: tcp connect to <a href="http://127.0.0.1:1023" target="_blank">127.0.0.1:1023</a> failed (Connection reset by peer)<br>
2009-01-12 10:38:18 E [server-protocol.c:7354:server_protocol_cleanup] server: invalid argument: cprivate<br>
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<br>
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<br>
2009-01-12 10:38:18 E [ib-verbs.c:213:__ib_verbs_disconnect] transport/ib-verbs: shutdown () - error: Transport endpoint is not connected<br>
<br>
Thanks for all the great work!<br><font color="#888888">
-- <br>
<br>
<br>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@nongnu.org" target="_blank">Gluster-devel@nongnu.org</a><br>
<a href="http://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">http://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Raghavendra G<br><br>