-
Notifications
You must be signed in to change notification settings - Fork 679
Weave Panic: reporting too much free space #1946
Comments
Thanks for the report. Which version of Weave Net are you running? |
@bboreham how do I get that version? I posted output
NOTE: I am not using weave proxy, just using weave router |
Ah, there is an earlier error in your log I had overlooked:
This (cryptic) message means that other peers on the network have an incompatible view of the IPAM data structure. Specifically, someone else has a ring entry at the same version number with different contents. I would expect lots of other errors and dropped connections on other peers. The only way forward is to shut down (using The "too much free space" message is basically a different manifestation of the same problem; if the data structure has got out of sync then the eventually-consistent approach fails. Lastly, it would be good to know how it got into this state. One potential route is listed in #678 (case 4); I imagine it will be very difficult to try to diagnose back to the original failure. |
you are correct, some of the other routers had that same issue. Our system automatically relaunches the weave containers if they die and they keep coming up with that same error. let me describe our use case, it might help in figuring out how we got here. In our environment we spin up and down servers constantly.
One interesting thing to note is that we can get into cases where all the peers that were passed to a server have been cycled through. But we call forget on them so I that should be fine. |
Ok, there's your problem. When you call We do mention this at http://docs.weave.works/weave/latest_release/ipam.html#stop, but I guess it's buried down a couple of levels in the documentation. |
Ran into this error today when trying to start weave container in my network.
command ran:
not sure what is going on here. never thought too much free space was a BAD things 😉
also, we do not use
--init-peer-count
. might be different then this old case #1463system info
The text was updated successfully, but these errors were encountered: