From e70c60ff032b1891773d5b16c24b7162fdaceb51 Mon Sep 17 00:00:00 2001 From: Jim Galasyn Date: Tue, 25 Apr 2017 12:34:18 -0700 Subject: [PATCH] Add engine ID error condition to UCP troubleshooting (#3057) --- .../monitor-and-troubleshoot/troubleshoot-node-messages.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/datacenter/ucp/2.1/guides/admin/monitor-and-troubleshoot/troubleshoot-node-messages.md b/datacenter/ucp/2.1/guides/admin/monitor-and-troubleshoot/troubleshoot-node-messages.md index cf06c0dbe5..5cf52ea423 100644 --- a/datacenter/ucp/2.1/guides/admin/monitor-and-troubleshoot/troubleshoot-node-messages.md +++ b/datacenter/ucp/2.1/guides/admin/monitor-and-troubleshoot/troubleshoot-node-messages.md @@ -1,7 +1,7 @@ --- title: Troubleshoot UCP Node States description: Learn how to troubleshoot individual UCP nodes. -keywords: Docker, UCP, troubleshoot, health +keywords: Docker, UCP, troubleshoot, health, swarm --- There are several cases in the lifecycle of UCP when a node is actively @@ -26,3 +26,4 @@ UCP node, their explanation, and the expected duration of a given step. | Reconfiguration pending | The target node is expected to be a manager but the `ucp-reconcile` container has not been started yet. | 1 - 10 seconds | | Unhealthy UCP Controller: node is unreachable | Other manager nodes of the cluster have not received a heartbeat message from the affected node within a predetermined timeout. This usually indicates that there's either a temporary or permanent interruption in the network link to that manager node. Please ensure the underlying networking infrastructure is operational and contact support if the symptom persists. | Until resolved | | Unhealthy UCP Controller: unable to reach controller | The controller that we are currently communicating with is not reachable within a predetermined timeout. Please refresh the node listing to see if the symptom persists. If the symptom appears intermittently, this could indicate latency spikes between manager nodes, which can lead to temporary loss in the availability of UCP itself. Please ensure the underlying networking infrastructure is operational and contact support if the symptom persists. | Until resolved | +| Unhealthy UCP Controller: Docker Swarm Cluster: Local node `` has status Pending | The Engine ID of an engine is not unique in the swarm. When a node first joins the cluster, it's added to the node inventory and discovered as `Pending` by Docker Swarm. The engine is "validated" if a `ucp-swarm-manager` container can connect to it via TLS, and if its Engine ID is unique in the swarm. If you see this issue repeatedly, make sure that your engines don't have duplicate IDs. Use `docker info` to see the Engine ID. Refresh the ID by removing the `/etc/docker/key.json` file and restarting the daemon. | Until resolved |