Commit
- Loading branch information
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -199,22 +199,49 @@ reports on the current status of the weave router and IP allocator: | |
| ```` | ||
| ... | ||
| Service: ipam | ||
| Consensus: achieved | ||
| Range: [10.32.0.0-10.48.0.0) | ||
| DefaultSubnet: 10.32.0.0/12 | ||
| ... | ||
| ```` | ||
|
|
||
| The first section covers the router; see the [troubleshooting | ||
| guide](troubleshooting.html#weave-status) for full details. | ||
|
|
||
| The 'Service: ipam' section, which is only present if weave has been | ||
| started with the `--ipalloc-range` option, displays the consensus | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong. 
awh
Author
Contributor
|
||
| state as well as the total allocation range and default subnet. | ||
This comment has been minimized.
Sorry, something went wrong. 
rade
Member
|
||
|
|
||
| Further information on the internal state of IPAM can be obtained from | ||
| `weave report`: | ||
|
|
||
| ```` | ||
| ... | ||
| "IPAM": { | ||
| "Paxos": null, | ||
| "Range": "[10.32.0.0-10.48.0.0)", | ||
| "DefaultSubnet": "10.32.0.0/12", | ||
| "Entries": [ | ||
| { | ||
| "Token": "10.32.0.0", | ||
| "Peer": "ce:31:e0:06:45:1a", | ||
| "Version": 5 | ||
| }, | ||
| { | ||
| "Token": "10.36.0.2", | ||
| "Peer": "ee:38:33:a7:d9:71", | ||
| "Version": 3 | ||
| }, | ||
| { | ||
| "Token": "10.40.0.0", | ||
| "Peer": "ea:2d:b2:e6:e4:f5", | ||
| "Version": 3 | ||
| } | ||
| ], | ||
| "PendingClaims": null, | ||
| "PendingAllocates": null | ||
| }, | ||
| ... | ||
| ```` | ||
This comment has been minimized.
Sorry, something went wrong. |
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,6 +5,14 @@ layout: default | |
|
|
||
| # Troubleshooting Weave | ||
|
|
||
| * [Overall status](#weave-status) | ||
| * [List connections](#weave-status-connections) | ||
| * [List peers](#weave-status-peers) | ||
| * [List DNS entries](#weave-status-dns) | ||
| * [JSON report](#weave-report) | ||
| * [List attached containers](#list-attached-containers) | ||
| * [Snapshot releases](#snapshot-releases) | ||
|
|
||
| Check what version of weave you are running with | ||
|
|
||
| weave version | ||
|
|
@@ -29,9 +37,6 @@ Another useful debugging technique is to attach standard packet | |
| capture and analysis tools, such as tcpdump and wireshark, to the | ||
| `weave` network bridge on the host. | ||
|
|
||
| To stop weave, run | ||
|
|
||
| weave stop | ||
|
|
@@ -50,100 +55,152 @@ Any running application containers will permanently lose connectivity | |
| with the weave network and have to be restarted in order to | ||
| re-connect. | ||
|
|
||
| ### <a name="weave-status"></a>Overall status | ||
|
|
||
| A status summary can be obtained with `weave status`: | ||
|
|
||
| ```` | ||
| $ weave status | ||
| Service: router | ||
| Name: 4a:0f:f6:ec:1c:93 | ||
| NickName: host1 | ||
| Encryption: disabled | ||
| PeerDiscovery: enabled | ||
| Peers: 3 | ||
| DirectPeers: 4 | ||
| Connections: 6 established, 0 unestablished, 3 failed | ||
| Service: ipam | ||
| Consensus: achieved | ||
| Range: [10.32.0.0-10.48.0.0) | ||
| DefaultSubnet: 10.32.0.0/12 | ||
| Service: dns | ||
| Domain: weave.local. | ||
| Address: 0.0.0.0:53 | ||
| TTL: 1 | ||
| Entries: 9 | ||
| Service: proxy | ||
| Address: tcp://127.0.0.1:12375 | ||
| ```` | ||
|
|
||
| The terms used here are explained further at | ||
| [how it works](how-it-works.html). | ||
|
|
||
| The 'Name' and 'NickName' lines identify the local weave router as a | ||
| peer in the weave network. The nickname defaults to the name of | ||
| the host on which the weave container was launched; if desired it can | ||
| be overriden by supplying the `--nickname` argument to `weave launch`. | ||
|
|
||
| The 'Encryption' line indicates whether | ||
| [encryption](features.html#security) is in use for communication | ||
| between peers. | ||
|
|
||
| The 'PeerDiscovery' line indicates whether | ||
| [automatic peer discovery](features.html#dynamic-topologies) is | ||
| enabled (which is the default). | ||
|
|
||
| 'Peers' is the total number of peers in the network. | ||
|
|
||
| 'DirectPeers' is the number of hosts specified to the local weave | ||
| router via `weave launch` or `weave connect`. | ||
|
|
||
| 'Connections' shows how many connections are in the 'established', | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
awh
Author
Contributor
|
||
| 'unestablished' and 'failed' states respectively. | ||
|
|
||
| There are further sections for the [IP address | ||
| allocator](ipam.html#troubleshooting), | ||
| [weaveDNS](weavedns.html#troubleshooting), and [Weave Docker API | ||
| Proxy](proxy.html#troubleshooting). | ||
|
|
||
| ### <a name="weave-status-connections"></a>List connections | ||
|
|
||
| Detailed information on connections can be obtained with `weave status | ||
This comment has been minimized.
Sorry, something went wrong. |
||
| connections`: | ||
|
|
||
| ```` | ||
| $ weave status connections | ||
| <- 192.168.48.12:39634 ea:2d:b2:e6:e4:f5(host2) direct established | ||
| <- 192.168.48.13:49619 ee:38:33:a7:d9:71(host3) discovered established | ||
| -> 192.168.48.14:6783 direct failed(dial tcp4 192.168.48.14:6783: no route to host), retry: 2015-08-05 13:19:00.550203683 +0000 UTC | ||
| -> 192.168.48.15:6783 direct failed(dial tcp4 192.168.48.15:6783: no route to host), retry: 2015-08-05 13:19:04.912851748 +0000 UTC | ||
| -> 192.168.48.16:6783 direct failed(dial tcp4 192.168.48.16:6783: no route to host), retry: 2015-08-05 13:18:56.609145605 +0000 UTC | ||
| ```` | ||
|
|
||
| The columns are as follows: | ||
|
|
||
| * Connection origination direction (-> for outbound, <- for inbound) | ||
| * Remote TCP address | ||
| * Remote peer name and nickname (omitted for failed connections) | ||
| * Type - `direct` if specified via `weave launch` or `weave connect`, | ||
| `discovered` if learned via gossip | ||
| * Status - `established` if TCP connection and corresponding UDP path | ||
| are up, `unestablished` if waiting for confirmation of UDP | ||
| heartbeat or `failed` if TCP connection could not be made | ||
|
|
||
| ### <a name="weave-status-peers"></a>List peers | ||
|
|
||
| Detailed information on peers can be obtained with `weave status | ||
| peers`: | ||
|
|
||
| ```` | ||
| $ weave status peers | ||
| ce:31:e0:06:45:1a(host1) | ||
| <- 192.168.48.12:39634 ea:2d:b2:e6:e4:f5(host2) established | ||
| <- 192.168.48.13:49619 ee:38:33:a7:d9:71(host3) established | ||
| ea:2d:b2:e6:e4:f5(host2) | ||
| -> 192.168.48.11:6783 ce:31:e0:06:45:1a(host1) established | ||
| <- 192.168.48.13:58181 ee:38:33:a7:d9:71(host3) established | ||
| ee:38:33:a7:d9:71(host3) | ||
| -> 192.168.48.12:6783 ea:2d:b2:e6:e4:f5(host2) established | ||
| -> 192.168.48.11:6783 ce:31:e0:06:45:1a(host1) established | ||
| ```` | ||
|
|
||
| This lists all peers known to this router, including itself. Each peer is | ||
| shown with its name and nickname, then each line thereafter shows another peer | ||
| that it is connected to, with the direction, IP address and port number of the | ||
| connection. In the above example, `host3` has connected to `host1` at | ||
| `192.168.48.11:6783`; `host1` sees the `host3` end of the same connection as | ||
| `192.168.48.13:49619`. | ||
|
|
||
| ### <a name="weave-status-dns"></a>List DNS entries | ||
|
|
||
| Detailed information on DNS registrations can be obtained with `weave | ||
| status dns`: | ||
|
|
||
| ```` | ||
| $ weave status dns | ||
| one 10.32.0.1 eebd81120ee4 4a:0f:f6:ec:1c:93 | ||
| one 10.43.255.255 4fcec78d2a9b 66:c4:47:c6:65:bf | ||
| one 10.40.0.0 bab69d305cba ba:98:d0:37:4f:1c | ||
| three 10.32.0.3 7615b6537f74 4a:0f:f6:ec:1c:93 | ||
| three 10.44.0.1 c0b39dc52f8d 66:c4:47:c6:65:bf | ||
| three 10.40.0.2 8a9c2e2ef00f ba:98:d0:37:4f:1c | ||
| two 10.32.0.2 83689b8f34e0 4a:0f:f6:ec:1c:93 | ||
| two 10.44.0.0 7edc306cb668 66:c4:47:c6:65:bf | ||
| two 10.40.0.1 68a5e9c2641b ba:98:d0:37:4f:1c | ||
| ```` | ||
|
|
||
| The columns are as follows: | ||
|
|
||
| * Unqualified hostname | ||
| * IPv4 address | ||
| * Registering entity identifier (typically a container ID) | ||
| * Name of peer from which the registration originates | ||
|
|
||
| ### <a name="weave-report"></a>JSON report | ||
|
|
||
| $ weave report | ||
|
|
||
| Produces a comprehensive dump of the internal state of the router, | ||
| IPAM and DNS services in JSON format, including all the information | ||
| available from the `weave status` commands. You can also supply a | ||
| Golang text template to `weave report` in a similar fashion to `docker | ||
| inspect`: | ||
|
|
||
| $ weave report -f '{{{.DNS.Domain}}' | ||
| weave.local. | ||
|
|
||
| ### <a name="list-attached-containers"></a>List attached containers | ||
|
|
||
|
|
||
That "is only present if ..." bit is wrong. Needs fixing in latest_release_doc_updates.