[BUG] ERROR GlusterFS vol_create failed
Pages: 1 2
admin
2,930 Posts
July 27, 2019, 5:11 pmQuote from admin on July 27, 2019, 5:11 pmno problem. i still would hope to know why this happens on your setup. could be a timing issue, maybe with how quickly assigned ips are activated. One thing you may want to test is during ip failover of iSCSI paths, do they work right away or do they take a long time to activate. I cannot think of other reasons.
no problem. i still would hope to know why this happens on your setup. could be a timing issue, maybe with how quickly assigned ips are activated. One thing you may want to test is during ip failover of iSCSI paths, do they work right away or do they take a long time to activate. I cannot think of other reasons.
majestic
13 Posts
July 27, 2019, 5:12 pmQuote from majestic on July 27, 2019, 5:12 pmThank you, will be testing this also to try and find why. Will report back when I know more.
Thank you, will be testing this also to try and find why. Will report back when I know more.
majestic
13 Posts
July 27, 2019, 5:52 pmQuote from majestic on July 27, 2019, 5:52 pmGood news, all resolved.
PEBCAK comes to mind (Problem Persists Between Chair And Keyboard).
It seems that I typo like six reinstalls or so and was "trying" to use an external IP (off AWS) lol.
I was meant to be using 10.227.3.0/24 and 10.227.4.0/24 but instead used 172.227.3.0/24 and 172.227.4.0/24 for the backend network.
After doing a gluster peer status on the second node, I could see it was trying to connect to AWS (who owns the 172.227 range).
I would suggest as a safety net, it might be a good idea to add a check in the installer to make sure you are using RFC1918 addresses.
Anyways, thanks very much for the help/tips/snippets, now I know a bit about gluster which i've not personally used before until now.
Now to testing cluster/failover etc 😉
Good news, all resolved.
PEBCAK comes to mind (Problem Persists Between Chair And Keyboard).
It seems that I typo like six reinstalls or so and was "trying" to use an external IP (off AWS) lol.
I was meant to be using 10.227.3.0/24 and 10.227.4.0/24 but instead used 172.227.3.0/24 and 172.227.4.0/24 for the backend network.
After doing a gluster peer status on the second node, I could see it was trying to connect to AWS (who owns the 172.227 range).
I would suggest as a safety net, it might be a good idea to add a check in the installer to make sure you are using RFC1918 addresses.
Anyways, thanks very much for the help/tips/snippets, now I know a bit about gluster which i've not personally used before until now.
Now to testing cluster/failover etc 😉
admin
2,930 Posts
July 27, 2019, 6:09 pmQuote from admin on July 27, 2019, 6:09 pmgreat..thanks for the feedback.
great..thanks for the feedback.
Pages: 1 2
[BUG] ERROR GlusterFS vol_create failed
admin
2,930 Posts
Quote from admin on July 27, 2019, 5:11 pmno problem. i still would hope to know why this happens on your setup. could be a timing issue, maybe with how quickly assigned ips are activated. One thing you may want to test is during ip failover of iSCSI paths, do they work right away or do they take a long time to activate. I cannot think of other reasons.
no problem. i still would hope to know why this happens on your setup. could be a timing issue, maybe with how quickly assigned ips are activated. One thing you may want to test is during ip failover of iSCSI paths, do they work right away or do they take a long time to activate. I cannot think of other reasons.
majestic
13 Posts
Quote from majestic on July 27, 2019, 5:12 pmThank you, will be testing this also to try and find why. Will report back when I know more.
Thank you, will be testing this also to try and find why. Will report back when I know more.
majestic
13 Posts
Quote from majestic on July 27, 2019, 5:52 pmGood news, all resolved.
PEBCAK comes to mind (Problem Persists Between Chair And Keyboard).
It seems that I typo like six reinstalls or so and was "trying" to use an external IP (off AWS) lol.
I was meant to be using 10.227.3.0/24 and 10.227.4.0/24 but instead used 172.227.3.0/24 and 172.227.4.0/24 for the backend network.
After doing a gluster peer status on the second node, I could see it was trying to connect to AWS (who owns the 172.227 range).
I would suggest as a safety net, it might be a good idea to add a check in the installer to make sure you are using RFC1918 addresses.
Anyways, thanks very much for the help/tips/snippets, now I know a bit about gluster which i've not personally used before until now.
Now to testing cluster/failover etc 😉
Good news, all resolved.
PEBCAK comes to mind (Problem Persists Between Chair And Keyboard).
It seems that I typo like six reinstalls or so and was "trying" to use an external IP (off AWS) lol.
I was meant to be using 10.227.3.0/24 and 10.227.4.0/24 but instead used 172.227.3.0/24 and 172.227.4.0/24 for the backend network.
After doing a gluster peer status on the second node, I could see it was trying to connect to AWS (who owns the 172.227 range).
I would suggest as a safety net, it might be a good idea to add a check in the installer to make sure you are using RFC1918 addresses.
Anyways, thanks very much for the help/tips/snippets, now I know a bit about gluster which i've not personally used before until now.
Now to testing cluster/failover etc 😉
admin
2,930 Posts
Quote from admin on July 27, 2019, 6:09 pmgreat..thanks for the feedback.
great..thanks for the feedback.