On 12/07/2011 10:03 PM, Matt Weil wrote: > > All, > > Is this normal? Can this be corrected? > > Thanks in advance for your responses. > >> [2011-12-06 17:56:59.48153] I >> [glusterd-rpc-ops.c:1243:glusterd3_1_commit_op_cbk] 0-glusterd: >> Received ACC from uuid: fc5e6659-a90a-4e25-a3a7-11de9a7de81d >> [2011-12-06 17:56:59.48811] I >> [glusterd-rpc-ops.c:1243:glusterd3_1_commit_op_cbk] 0-glusterd: >> Received ACC from uuid: d1216f43-2ae6-42bd-a597-c0ab6a101d6b >> [2011-12-06 17:56:59.49073] I >> [glusterd-rpc-ops.c:1243:glusterd3_1_commit_op_cbk] 0-glusterd: >> Received ACC from uuid: 4bf94e6e-69ca-4d51-9a85-c1d98a95325d >> [2011-12-06 17:56:59.49137] I >> [glusterd-rpc-ops.c:1243:glusterd3_1_commit_op_cbk] 0-glusterd: >> Received ACC from uuid: 154cdbb2-6a53-449d-b6e3-bfd84091d90c >> [2011-12-06 17:56:59.49567] I >> [glusterd-rpc-ops.c:1243:glusterd3_1_commit_op_cbk] 0-glusterd: >> Received ACC from uuid: 4c9d68d6-d573-43d0-aec5-07173c1699d0 >> [2011-12-06 17:56:59.49803] I >> [glusterd-rpc-ops.c:818:glusterd3_1_cluster_unlock_cbk] 0-glusterd: >> Received ACC from uuid: fc5e6659-a90a-4e25-a3a7-11de9a7de81d >> [2011-12-06 17:56:59.49850] I >> [glusterd-rpc-ops.c:818:glusterd3_1_cluster_unlock_cbk] 0-glusterd: >> Received ACC from uuid: d1216f43-2ae6-42bd-a597-c0ab6a101d6b >> [2011-12-06 17:56:59.50228] I >> [glusterd-rpc-ops.c:818:glusterd3_1_cluster_unlock_cbk] 0-glusterd: >> Received ACC from uuid: 4bf94e6e-69ca-4d51-9a85-c1d98a95325d >> [2011-12-06 17:56:59.50285] I >> [glusterd-rpc-ops.c:818:glusterd3_1_cluster_unlock_cbk] 0-glusterd: >> Received ACC from uuid: 154cdbb2-6a53-449d-b6e3-bfd84091d90c >> [2011-12-06 17:56:59.50346] I >> [glusterd-rpc-ops.c:818:glusterd3_1_cluster_unlock_cbk] 0-glusterd: >> Received ACC from uuid: 4c9d68d6-d573-43d0-aec5-07173c1699d0 >> [2011-12-06 17:56:59.50375] I >> [glusterd-op-sm.c:7250:glusterd_op_txn_complete] 0-glusterd: Cleared >> local lock >> [2011-12-06 17:56:59.52105] W >> [socket.c:1494:__socket_proto_state_machine] 0-socket.management: >> reading from socket failed. Error (Transport endpoint is not >> connected), peer (127.0.0.1:694) >> [2011-12-06 17:56:59.168257] W >> [socket.c:1494:__socket_proto_state_machine] 0-socket.management: >> reading from socket failed. Error (Transport endpoint is not >> connected), peer (10.0.30.11:730) >> [2011-12-06 17:56:59.168357] W >> [socket.c:1494:__socket_proto_state_machine] 0-socket.management: >> reading from socket failed. Error (Transport endpoint is not >> connected), peer (10.0.30.11:728) >> [2011-12-06 17:56:59.168441] W >> [socket.c:1494:__socket_proto_state_machine] 0-socket.management: >> reading from socket failed. Error (Transport endpoint is not >> connected), peer (10.0.30.11:726) >> [2011-12-06 17:56:59.168503] W >> [socket.c:1494:__socket_proto_state_machine] 0-socket.management: >> reading from socket failed. Error (Transport endpoint is not >> connected), peer (10.0.30.11:724) >> [2011-12-06 17:56:59.168591] W >> [socket.c:1494:__socket_proto_state_machine] 0-socket.management: >> reading from socket failed. Error (Transport endpoint is not >> connected), peer (10.0.30.11:722) >> [2011-12-06 17:56:59.168672] W >> [socket.c:1494:__socket_proto_state_machine] 0-socket.management: >> reading from socket failed. Error (Transport endpoint is not >> connected), peer (10.0.30.11:720) >> [2011-12-06 17:56:59.169287] W >> [socket.c:1494:__socket_proto_state_machine] 0-socket.management: >> reading from socket failed. Error (Transport endpoint is not >> connected), peer (10.0.30.15:730) >> [2011-12-06 17:56:59.169359] W >> [socket.c:1494:__socket_proto_state_machine] 0-socket.management: >> reading from socket failed. Error (Transport endpoint is not >> connected), peer (10.0.30.15:728) >> [2011-12-06 17:56:59.169398] W >> [socket.c:1494:__socket_proto_state_machine] 0-socket.management: >> reading from socket failed. Error (Transport endpoint is not >> connected), peer (10.0.30.13:730) >> [2011-12-06 17:56:59.169438] W >> [socket.c:1494:__socket_proto_state_machine] 0-socket.management: >> reading from socket failed. Error (Transport endpoint is not >> connected), peer (10.0.30.13:728) >> [2011-12-06 17:56:59.169476] W >> [socket.c:1494:__socket_proto_state_machine] 0-socket.management: >> reading from socket failed. Error (Transport endpoint is not >> connected), peer (10.0.30.15:726) >> [2011-12-06 17:56:59.169529] W >> [socket.c:1494:__socket_proto_state_machine] 0-socket.management: >> reading from socket failed. Error (Transport endpoint is not >> connected), peer (10.0.30.13:726) >> [2011-12-06 17:56:59.169581] W >> [socket.c:1494:__socket_proto_state_machine] 0-socket.management: >> reading from socket failed. Error (Transport endpoint is not >> connected), peer (10.0.30.13:724) > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users Dont worry about it. We fixed this message in glusterd for future releases. Pranith.
