[Gluster-users] Transport endpoint is not connected
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@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] Transport endpoint is not connected
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@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. ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] Transport endpoint is not connected
This looks like the messages that were worrying me. I'm still getting timeouts on nfs mounts. Bill Sebok Computer Software Manager, Univ. of Maryland, Astronomy Internet: w...@astro.umd.eduURL: http://furo.astro.umd.edu/ On Wed, Dec 07, 2011 at 10:33:58AM -0600, 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 --- etc. ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] Transport endpoint is not connected
On 12/07/2011 11:07 PM, William L. Sebok wrote: This looks like the messages that were worrying me. I'm still getting timeouts on nfs mounts. Bill Sebok Computer Software Manager, Univ. of Maryland, Astronomy Internet: w...@astro.umd.eduURL: http://furo.astro.umd.edu/ On Wed, Dec 07, 2011 at 10:33:58AM -0600, 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 --- etc. ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users William, In which log do you see the messages?. Pranith ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] Transport endpoint is not connected
On Wed, Dec 07, 2011 at 11:16:54PM +0530, Pranith Kumar K wrote: William, In which log do you see the messages?. Pranith /var/log/etc-glusterfs-glusterd.vol.log on any of the servers. I now have determined that I need to add a nfsvers=3 on mount on the client I was using as a test. The client is running Scientific Linux 6.1 and probably was defaulting to nfs 4. That was the source of my nfs timeouts. Sorry about that. - Bill Sebok Computer Software Manager, Univ. of Maryland, Astronomy Internet: w...@astro.umd.eduURL: http://furo.astro.umd.edu/ ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
[Gluster-users] folders with no permissions.
Just some simply iozone testing failed due to folder permissions. The tmp folder is created by iozone. six nodes with stripe 6 and underlying EXT4 file system. The ext4 filesystems where not mounted with the -o acl option. Any Ideas? in both cases it created a folder with no permissions. 188K d- 2 rootroot 24K 2011-12-06 11:28 tmp/ iozone$ rm -rf tmp rm: cannot remove directory `tmp': Permission denied test$ cd iozone.broke/ iozone.broke$ ls ./ ../ tmp/ iozone.broke$ ls -lash total 580K 288K drwxrwxrwx 6 rootroot 24K 2011-12-04 14:28 ../ 4.0K d- 2 rootroot 4.0K 2011-12-06 11:32 tmp/ each node has error trying to set permissions on that folder. [2011-12-06 12:23:36.593604] E [marker.c:2018:marker_setattr_cbk] 0-gluster1-marker: Operation not permitted occured during setattr of nul [2011-12-06 12:23:36.593669] I [server3_1-fops.c:1526:server_setattr_cbk] 0-gluster1-server: 433: SETATTR /test/iozone/tmp (-734804259) == -1 (Operation not permitted) [2011-12-06 12:23:36.593669] I [server3_1-fops.c:1526:server_setattr_cbk] 0-gluster1-server: 433: SETATTR /test/iozone/tmp (-734804259) == -1 (Operation not permitted) 188K d- 2 rootroot 24K 2011-12-06 11:28 tmp/ iozone$ chmod +rw tmp/ chmod: changing permissions of `tmp/': Operation not permitted iozone$ ls -lash ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] folders with no permissions.
On 12/7/11 12:53 PM, Matt Weil wrote: Just some simply iozone testing failed due to folder permissions. The tmp folder is created by iozone. six nodes with stripe 6 and underlying EXT4 file system. The ext4 filesystems where not mounted with out the -o acl option. I meant with out the -o acl option. Any Ideas? in both cases it created a folder with no permissions. 188K d- 2 root root 24K 2011-12-06 11:28 tmp/ iozone$ rm -rf tmp rm: cannot remove directory `tmp': Permission denied test$ cd iozone.broke/ iozone.broke$ ls ./ ../ tmp/ iozone.broke$ ls -lash total 580K 288K drwxrwxrwx 6 root root 24K 2011-12-04 14:28 ../ 4.0K d- 2 root root 4.0K 2011-12-06 11:32 tmp/ each node has error trying to set permissions on that folder. [2011-12-06 12:23:36.593604] E [marker.c:2018:marker_setattr_cbk] 0-gluster1-marker: Operation not permitted occured during setattr of nul [2011-12-06 12:23:36.593669] I [server3_1-fops.c:1526:server_setattr_cbk] 0-gluster1-server: 433: SETATTR /test/iozone/tmp (-734804259) == -1 (Operation not permitted) [2011-12-06 12:23:36.593669] I [server3_1-fops.c:1526:server_setattr_cbk] 0-gluster1-server: 433: SETATTR /test/iozone/tmp (-734804259) == -1 (Operation not permitted) 188K d- 2 root root 24K 2011-12-06 11:28 tmp/ iozone$ chmod +rw tmp/ chmod: changing permissions of `tmp/': Operation not permitted iozone$ ls -lash ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
[Gluster-users] syslog options for gluster
are there any options to have glusterd use syslog? Would like the logs to go to a central server. Thanks Matt ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
Re: [Gluster-users] syslog options for gluster
On 12/08/2011 12:33 AM, Matt Weil wrote: are there any options to have glusterd use syslog? Would like the logs to go to a central server. bash# gluster volume set VOLNAME [client|brick].syslog-level WARNING # or any log level you want. Currently GlusterFS logs any logs of CRITICAL and above severity into syslog. Regards, Amar ___ Gluster-users mailing list Gluster-users@gluster.org http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
