I dont know if this will resolve the issue but it seems that if you restart the glusterd service it might stop. Seen some mention of restarting glusterd to get rid of similar messages in the logs and I tried it. Dont seem to get any more of the [2012-02-21 17:25:27.618225] W [socket.c:1494:__socket_proto_state_machine] 0-socket.management: reading from socket failed. Error (Transport endpoint is not connected), peer (10.131.139.26:1019) But i still get the following when ever i do a gluster cli command, like gluster volume info all [2012-02-25 20:14:09.667026] I [glusterd-handler.c:796:glusterd_handle_cli_get_volume] 0-glusterd: Received get vol req [2012-02-25 20:14:15.246956] 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:1020) And I cant figure out why I get the socket error with 127.0.0.1 I have checked all network configurations/dns on the server. And the setup is made by following the online manual for 3.2.5 for a replicated setup on 2 servers... Again I should point out that Im not suffering any performance issues or other problems with using the setup. Im just curious why I get theese warnings in the logs with such a basic setup as mine. It makes me paranoid that I have some problem in my setup that might cause troubble further down the road when I scale things up. Edit: Doing gluster volume info all on a server with 2 volumes and total of 4 bricks gives the following in the etc log: [2012-02-25 20:20:59.917682] I [glusterd-handler.c:796:glusterd_handle_cli_get_volume] 0-glusterd: Received get vol req [2012-02-25 20:20:59.943092] I [glusterd-handler.c:796:glusterd_handle_cli_get_volume] 0-glusterd: Received get vol req [2012-02-25 20:20:59.943470] I [glusterd-handler.c:796:glusterd_handle_cli_get_volume] 0-glusterd: Received get vol req [2012-02-25 20:21:02.348626] 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:1023) Doing gluster volume info <one of the vol names> gives just this in the etc log: [2012-02-25 20:23:32.478744] I [glusterd-handler.c:796:glusterd_handle_cli_get_volume] 0-glusterd: Received get vol req [2012-02-25 20:23:32.480538] 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:1023) Im confused... Cheers --- Carl Boberg Operations Memnon Networks AB Tegn?rgatan 34, SE-113 59 Stockholm Mobile: +46(0)70 467 27 12 www.memnonnetworks.com On Sat, Feb 25, 2012 at 16:30, Dan Bretherton <d.a.bretherton at reading.ac.uk>wrote: > (Re-sending with correct subject - sorry) > > Hello Carl and list members, > > My etc-glusterfs-glusterd.vol.log files are also flooded with warning > messages like the following. > > bdan4: [2012-01-05 18:54:30.385095] W [socket.c:1494:__socket_proto_**state_machine] > 0-socket.management: reading from socket failed. Error (Transport endpoint > is not connected), peer (192.171.166.72:993) > > Some of the "peers" mentioned are actually clients but others are > GlusterFS servers. The warnings seem to occur repeatedly for a period of > time on all the servers and then stop for a while before starting again. I > have a feeling it has something to do with NFS, because it seems to occur > more frequently on servers I use to export NFS (although all are running > the glusterfs NFS process). The warnings seem to coincide with the NFS > processes restarting, as they did on all the servers in my cluster at 16:48 > today, un-noticed by me, for no apparent reason. The warnings stopped on > most servers soon after this, but they have carried on since then on the > servers that are exporting NFS. > > I have been ignoring these warnings for some time because there didn't > seem to be any adverse effects, but I am trying to solve a serious > performance problem affecting some applications and I want to look at all > possible causes for concern. I have seen these warnings in log files > posted to the list in the context of various problems which I don't have, > but I have never seen them mentioned specifically. Are these spurious > warnings that can be ignored or do they point to a problem with my cluster? > Any comments or suggestions would be much appreciated. > > Regards > Dan. > > > On 02/23/2012 10:01 PM, gluster-users-request at gluster.**org<gluster-users-request at gluster.org>wrote: > >> Date: Thu, 23 Feb 2012 22:49:52 +0100 >> From: Carl Boberg<carl.boberg@**memnonnetworks.com<carl.boberg at memnonnetworks.com> >> > >> Subject: Help with some socket related logwarnings >> To:gluster-users at gluster.org >> Message-ID: >> <CANnFLQwZHpjrVkHCrME0wWFBUFs_**ZJQv1dWVHBQRi6HSkTDQag at mail.** >> gmail.com<CANnFLQwZHpjrVkHCrME0wWFBUFs_ZJQv1dWVHBQRi6HSkTDQag at mail.gmail.com> >> > >> Content-Type: text/plain; charset="iso-8859-1" >> >> >> Hello >> >> I have just started to prepare a smallish production setup (nothing >> critical running on it yet). >> >> I have 2 gluster servers with 8 volumes and Im getting a lot of theese >> warnings in the cli.log >> [2012-02-23 22:32:15.808271] W [rpc-transport.c:606:rpc_**transport_load] >> 0-rpc-transport: missing 'option transport-type'. defaulting to "socket" >> >> Could be related to the warinings in the etc-glusterfs-glusterd.vol.log >> [2012-02-21 17:28:15.279406] W [socket.c:1494:__socket_proto_** >> state_machine] >> 0-socket.management: reading from socket failed. Error (Transport endpoint >> is not connected), peer (10.131.139.26:1019) >> [2012-02-21 17:28:15.279521] W [socket.c:1494:__socket_proto_** >> state_machine] >> 0-socket.management: reading from socket failed. Error (Transport endpoint >> is not connected), peer (10.131.139.26:1016) >> [2012-02-21 17:28:19.236986] W [socket.c:1494:__socket_proto_** >> state_machine] >> 0-socket.management: reading from socket failed. Error (Transport endpoint >> is not connected), peer (10.131.139.25:1013) >> [2012-02-21 17:28:42.660021] 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:1012) >> [2012-02-21 17:34:58.405575] W [socket.c:1494:__socket_proto_** >> state_machine] >> 0-socket.management: reading from socket failed. Error (Transport endpoint >> is not connected), peer (10.131.139.9:1021) >> >> >> where 10.131.139.26 and 25 are the 2 servers and 10.131.139.9 is a client >> (other clients ip:s are also showing up) >> >> 'gluster peer status' on either server says everything is fine and >> connected and im not experiencing any problems. Im just a little nervous >> about the warnings since they get logged quite often. Would be greatful >> for >> som insight in the reason for theese warnings. >> >> gluster 3.2.5 rpm install >> all clients and servers are RedHat 6.1 using native client >> >> Best regards >> --- >> Carl Boberg >> Operations >> >> Memnon Networks AB >> Tegn?rgatan 34, SE-113 59 Stockholm >> >> >> Mobile: +46(0)70 467 27 12 >> www.memnonnetworks.com >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gluster.org/pipermail/gluster-users/attachments/20120225/5264a020/attachment-0001.htm>
