On 02/26/2012 01:30 AM, Brian Candler wrote:
On Sat, Feb 25, 2012 at 08:27:06PM +0100, Carl Boberg wrote:
[socket.c:1494:__socket_proto_state_machine] 0-socket.management:
reading from socket failed. Error (Transport endpoint is not
connected), peer ([2]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.
Including /etc/hosts? That is, you don't have an entry like
127.0.0.1 myhostname
(Some distros have a habit of adding an entry like that for you)
____________________________________
Can you please check if your 'glusterd.vol' file (located in
/etc/glusterfs/glusterd.vol) has below lines?
" option transport.socket.read-fail-log off"
If not, you can go ahead and add it.
Dan, to answer your question, this log in 'glusterd.log' file is not
serious. But it gives a hint of possible network issues in Filesystem
logs (like brick logs and nfs logs and native client logs), as in
Filesystem setup we need to be connected all the time.
Regards,
Amar
_______________________________________________
Gluster-users mailing list
[email protected]
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
