Node interfaces do not match cluster interface settings
Pages: 1 2
afrima
17 Posts
February 21, 2018, 4:20 pmQuote from afrima on February 21, 2018, 4:20 pm
Quote from admin on February 21, 2018, 4:15 pm
Yes of course it can accept any nodes at any time.
I just want you to try the other 2 nodes ( or any one of them) to rule out any configuration issue with current node.
Also have you changed the cluster config manually, if so do let me know what changed.
Cheers Hatem
No i haven't changed anything on cluster config manually.
i'll try another machine and let you know.
Quote from admin on February 21, 2018, 4:15 pm
Yes of course it can accept any nodes at any time.
I just want you to try the other 2 nodes ( or any one of them) to rule out any configuration issue with current node.
Also have you changed the cluster config manually, if so do let me know what changed.
Cheers Hatem
No i haven't changed anything on cluster config manually.
i'll try another machine and let you know.
afrima
17 Posts
February 21, 2018, 6:05 pmQuote from afrima on February 21, 2018, 6:05 pmI tried it on other nodes, it gives me the same error after almost an hour trying to join the cluster:
Error building cluster, please check detail below.
Error List
Could not commit node.
Download Cluster State Logs
and when i want to download the cluster state log it gives me "internal Server Error"!
I tried it on other nodes, it gives me the same error after almost an hour trying to join the cluster:
Error building cluster, please check detail below.
Error List
Could not commit node.
Download Cluster State Logs
and when i want to download the cluster state log it gives me "internal Server Error"!
admin
2,930 Posts
February 21, 2018, 6:08 pmQuote from admin on February 21, 2018, 6:08 pmCan you please send email me the log file
/opt/petasan/log/PetaSAN.log
as well as
/etc/hosts
to
contact-us @ petasan.org
Can you please send email me the log file
/opt/petasan/log/PetaSAN.log
as well as
/etc/hosts
to
contact-us @ petasan.org
Last edited on February 21, 2018, 6:09 pm by admin · #13
admin
2,930 Posts
February 21, 2018, 6:35 pmQuote from admin on February 21, 2018, 6:35 pmThe error looks like the new node cannot find the consul servers. so in addition to the earlier post:
For the first 3 nodes, can you run:
consul members
consul info | grep leader
For the failed node:
Can you ping on the backend 1 ip of the first 3 nodes ?
cat /opt/petasan/config/cluster_info.json
cat /etc/hosts
The error looks like the new node cannot find the consul servers. so in addition to the earlier post:
For the first 3 nodes, can you run:
consul members
consul info | grep leader
For the failed node:
Can you ping on the backend 1 ip of the first 3 nodes ?
cat /opt/petasan/config/cluster_info.json
cat /etc/hosts
Last edited on February 21, 2018, 6:36 pm by admin · #14
afrima
17 Posts
February 22, 2018, 1:58 pmQuote from afrima on February 22, 2018, 1:58 pmpinging from backend 1 to the other 3 nodes i noticed a problem with the switch configuration which didn't allow the backend traffic to go through backend vlan!!
Anyways, playing on the switch side, and your hints, solved the problem.
Thanks for the Help.
we'll keep on exploring your tool 😉
pinging from backend 1 to the other 3 nodes i noticed a problem with the switch configuration which didn't allow the backend traffic to go through backend vlan!!
Anyways, playing on the switch side, and your hints, solved the problem.
Thanks for the Help.
we'll keep on exploring your tool 😉
Pages: 1 2
Node interfaces do not match cluster interface settings
afrima
17 Posts
Quote from afrima on February 21, 2018, 4:20 pmQuote from admin on February 21, 2018, 4:15 pmYes of course it can accept any nodes at any time.
I just want you to try the other 2 nodes ( or any one of them) to rule out any configuration issue with current node.
Also have you changed the cluster config manually, if so do let me know what changed.
Cheers Hatem
No i haven't changed anything on cluster config manually.
i'll try another machine and let you know.
Quote from admin on February 21, 2018, 4:15 pmYes of course it can accept any nodes at any time.
I just want you to try the other 2 nodes ( or any one of them) to rule out any configuration issue with current node.
Also have you changed the cluster config manually, if so do let me know what changed.
Cheers Hatem
No i haven't changed anything on cluster config manually.
i'll try another machine and let you know.
afrima
17 Posts
Quote from afrima on February 21, 2018, 6:05 pmI tried it on other nodes, it gives me the same error after almost an hour trying to join the cluster:
Error building cluster, please check detail below.
Error List
Could not commit node.
Download Cluster State Logsand when i want to download the cluster state log it gives me "internal Server Error"!
I tried it on other nodes, it gives me the same error after almost an hour trying to join the cluster:
Error building cluster, please check detail below.
Error List
Could not commit node.
admin
2,930 Posts
Quote from admin on February 21, 2018, 6:08 pmCan you please send email me the log file
/opt/petasan/log/PetaSAN.log
as well as
/etc/hosts
to
contact-us @ petasan.org
Can you please send email me the log file
/opt/petasan/log/PetaSAN.log
as well as
/etc/hosts
to
contact-us @ petasan.org
admin
2,930 Posts
Quote from admin on February 21, 2018, 6:35 pmThe error looks like the new node cannot find the consul servers. so in addition to the earlier post:
For the first 3 nodes, can you run:
consul members
consul info | grep leaderFor the failed node:
Can you ping on the backend 1 ip of the first 3 nodes ?
cat /opt/petasan/config/cluster_info.json
cat /etc/hosts
The error looks like the new node cannot find the consul servers. so in addition to the earlier post:
For the first 3 nodes, can you run:
consul members
consul info | grep leader
For the failed node:
Can you ping on the backend 1 ip of the first 3 nodes ?
cat /opt/petasan/config/cluster_info.json
cat /etc/hosts
afrima
17 Posts
Quote from afrima on February 22, 2018, 1:58 pmpinging from backend 1 to the other 3 nodes i noticed a problem with the switch configuration which didn't allow the backend traffic to go through backend vlan!!
Anyways, playing on the switch side, and your hints, solved the problem.
Thanks for the Help.
we'll keep on exploring your tool 😉
pinging from backend 1 to the other 3 nodes i noticed a problem with the switch configuration which didn't allow the backend traffic to go through backend vlan!!
Anyways, playing on the switch side, and your hints, solved the problem.
Thanks for the Help.
we'll keep on exploring your tool 😉