The glusterfs-core RPM installs the glusterd daemon and sets it to start
automatically. I figured this wasn't needed on clients, so I turned it
off. However, I now see tons of messages like this in the logs of the
servers:
[2011-05-06 00:03:57.253243] W [socket.c:1494:__socket_proto_state_machine]
0-socket.management: reading from socket failed. Error (Transport endpoint is
not connected), peer (172.19.12.160:1022)
where 172.19.12.160 is an example client address. The simple tests I've
run seem to work (file creation, can see new files from other clients,
etc). But the warning message gave me pause.
--
Joshua Baker-LePain
QB3 Shared Cluster Sysadmin
UCSF
_______________________________________________
Gluster-users mailing list
[email protected]
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
