Re: Ip based peer probe volume create error

Gaurav Yadav <gyadav@xxxxxxxxxx> · Thu, 8 Feb 2018 00:15:55 +0530

From glusterd.logs, It looks like address resolution issue in "glusterd_brickinfo_new_from_brick" functon call.

After seeing command history, I could see that you have 3 nodes, and firstly you are peer probing 51.15.90.60  and  163.172.151.120 from  51.15.77.14
So here itself you have 3 node cluster, after all this you are going on node 2 and again peer probing 51.15.77.14.
 Ideally it should work, with above steps, but due to some address resolution volume create is getting failed, and from glusterd logs its not clear.

For a workaround could you please try avoiding peer probing again from node 2 and give a try.

Meanwhile for further debugging could you please send us  glusterd debug logs. 

On Wed, Feb 7, 2018 at 9:18 PM, Ercan Aydoğan <ercan.aydogan@xxxxxxxxx> wrote:
Hi,
i attached logs.

node3_cmd_history.log is empty because i did not run any command on node3.

At logs i saw node 1 peer status contains ip addresses as peer. But other nodes node1 visible at it’s name .

node 1 peer status is 

root@pri:/var/log/glusterfs# gluster peer status
Number of Peers: 2

Hostname: 51.15.90.60
Uuid: eed0d6c6-90ef-4705-b3f9-0b028d769df3
State: Peer in Cluster (Connected)

Hostname: 163.172.151.120
Uuid: 42bc6ec5-5826-4a40-b2d3-8a34e6caabb7
State: Peer in Cluster (Connected)

node 2 

root@sec:/var/log/glusterfs# gluster peer status
Number of Peers: 2

Hostname: pri.ostechnix.lan
Uuid: 700fb496-4270-4e2a-878e-1a93ea0a5d0c
State: Peer in Cluster (Connected)
Other names:
51.15.77.14

Hostname: 163.172.151.120
Uuid: 42bc6ec5-5826-4a40-b2d3-8a34e6caabb7
State: Peer in Cluster (Connected)

node 3

root@third:/var/log/glusterfs# gluster peer status
Number of Peers: 2

Hostname: pri.ostechnix.lan
Uuid: 700fb496-4270-4e2a-878e-1a93ea0a5d0c
State: Peer in Cluster (Connected)
Other names:
51.15.77.14

Hostname: 51.15.90.10
Uuid: eed0d6c6-90ef-4705-b3f9-0b028d769df3
State: Peer in Cluster (Connected)

On 7 Feb 2018, at 18:14, Gaurav Yadav <gyadav@xxxxxxxxxx> wrote:

Hi,

Could you please send me the glusterd.logs and cmd-history logs from all the nodes.

Thanks
Gaurav

On Wed, Feb 7, 2018 at 5:13 PM, Ercan Aydoğan <ercan.aydogan@xxxxxxxxx> wrote:
Hello,
i have dedicated 3.11.3 version glusterfs 3 nodes. i can create volumes if peer probe with  hostname.

But ip based probe it’s not working.

What’s the correct /etc/hosts and hostname values when ip based peer probe.

Do i need still need peer FQDN names on /etc/hosts .

i need advice how can fix this issue.

_______________________________________________

Gluster-users mailing list

Gluster-users@xxxxxxxxxxx

http://lists.gluster.org/mailman/listinfo/gluster-users

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users