(null)
I'm not sure if the system's privileged ports are exausted.
Also I'm trying to set ping-timeout in /etc/glusterfs/glusterd.vol to a
larger value, will this help?
Many thanks.
2015-09-01 16:18 GMT+08:00 Vijay Bellur <vbel...@redhat.com>:
> On Tuesday 01 September 2015 09
I've tried both: assuming server1 is already in pool, server2 is undergoing
peer-probing
server2:~$ mount server1:/vol1 mountpoint, fail;
server2:~$ mount server2:/vol1 mountpoint, fail.
Strange enough. I *should* be able to mount server1:/vol1 on server2. But
this is not the case :(
Maybe
do in such situation? Do I need to wait for the whole peer
probing progress to complete, or can I simply kill the glusterd and restart
it?
Regards,
Yiping Peng
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman
:39:01.145074] I [MSGID: 106502]
[glusterd-handler.c:2751:__glusterd_handle_friend_update] 0-management:
Received my uuid as Friend
[2015-08-31 09:39:01.406146] W [socket.c:923:__socket_keepalive] 0-socket:
failed to set TCP_USER_TIMEOUT -1000 on socket 12, Protocol not available
[2015-08-31 09:39:01.406168] E [so
this, will the currently mounted volumes become unavailable?
2015-08-31 17:47 GMT+08:00 Yiping Peng <barius...@gmail.com>:
> The "Disconnected" state of nodes randomly changes, so I randomly picked a
> node and tailed last several lines
> of /var/log/glusterfs/etc-g
