-
Notifications
You must be signed in to change notification settings - Fork 673
"all IP ranges owned by unreachable peers" - with no unreachable peers #1875
Comments
Looks like this may be a dupe of #894 ? |
Can you do |
Same output on all 3 hosts: If the MAC-like strings are relevant to debugging, please let me know. |
The mac-like string is a randomly-chosen ID for each peer. When you restart a peer it comes back with a new ID - if you look at That being the case, you can you do |
Thank you for the explanation & info on how to debug issues. That worked. :) This does feel horribly broken. It seems to me like: Would help build a more robust system. |
Note that #1866 will (once completed) address the proximate cause, by not changing the identity of the peer. (A) this is a very deliberate choice. See, for instance, http://blog.weave.works/2015/11/03/docker-networking-1-9-technical-deep-dive/ We are very keen on a robust system, but perhaps select different factors as pre-eminent. Note that consensus protocols simply halt in the presence of (enough) uncontactable nodes. |
I'm going to close this as a duplicate of #894 |
weave is no longer assigning IP addresses. When I type
weave status
, I get "all IP ranges owned by unreachable peers - use 'rmpeer' if they are dead".On every host:
weave status peers
shows a list of all the other peers, all of which are active connections.weave status targets
shows a list of all the other targets, all of which there are connections toweave status connections
shows an active connection to every other hostIndividual hosts in the weave mesh have been restarted frequently during various testing & configuration activities, but the mesh has been kept up and running. There aren't any currently inactive peers listed for me to
rmpeer
.The text was updated successfully, but these errors were encountered: