From 90e6ecdd11a872bcbea3e660fe7a387d6368c101 Mon Sep 17 00:00:00 2001 From: Bryan Boreham Date: Fri, 23 Mar 2018 14:10:05 +0000 Subject: [PATCH 1/3] Add 'peer names collision' to FAQ --- site/faq.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/site/faq.md b/site/faq.md index 7afc207c..822a3c77 100644 --- a/site/faq.md +++ b/site/faq.md @@ -40,6 +40,15 @@ A simple way to accomplish this would be to run Weave on the host and then run, Yet another option is to expose a port from the container on host B and then connect to it. You can read about exposing ports in [Exporting Services](/site/tasks/manage/service-management.md#exporting). + +**Q: Why am I seeing "peer names collision" and failed connections?** + +This sometimes happens when machines are cloned; we require each +machine in your cluster to have a unique identity. + +For more information see [Peer Names](/site/operational-guide/concepts.md#peer-name). + + **Q: Why am I seeing the same IP address assigned to two different containers on different hosts?** From b3f26f00e242a25e783b7ff33940391a77ee86ef Mon Sep 17 00:00:00 2001 From: Bryan Boreham Date: Fri, 23 Mar 2018 14:55:54 +0000 Subject: [PATCH 2/3] Add some hints how to set the unique ID --- site/faq.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/site/faq.md b/site/faq.md index 822a3c77..035031ee 100644 --- a/site/faq.md +++ b/site/faq.md @@ -48,6 +48,9 @@ machine in your cluster to have a unique identity. For more information see [Peer Names](/site/operational-guide/concepts.md#peer-name). +Depending on your Linux distribution you may need to [set up +machine-id](https://www.freedesktop.org/software/systemd/man/machine-id.html) +or [generate a dbus id](https://dbus.freedesktop.org/doc/dbus-uuidgen.1.html). **Q: Why am I seeing the same IP address assigned to two different containers on different hosts?** From a439288765a585c6c8c8f90d7728e99a13e87e31 Mon Sep 17 00:00:00 2001 From: Bryan Boreham Date: Tue, 27 Mar 2018 21:06:41 +0000 Subject: [PATCH 3/3] Raise weave-kube default connection limit from 30 to 100 This was missed from 265bfcf --- prog/weave-kube/launch.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/prog/weave-kube/launch.sh b/prog/weave-kube/launch.sh index d605a7bf..c8ba8ebf 100755 --- a/prog/weave-kube/launch.sh +++ b/prog/weave-kube/launch.sh @@ -29,7 +29,7 @@ IPALLOC_RANGE=${IPALLOC_RANGE:-10.32.0.0/12} HTTP_ADDR=${WEAVE_HTTP_ADDR:-127.0.0.1:6784} STATUS_ADDR=${WEAVE_STATUS_ADDR:-0.0.0.0:6782} HOST_ROOT=${HOST_ROOT:-/host} -CONN_LIMIT=${CONN_LIMIT:-30} +CONN_LIMIT=${CONN_LIMIT:-100} DB_PREFIX=${DB_PREFIX:-/weavedb/weave-net} # Check if the IP range overlaps anything existing on the host