Troubleshoot UCP node statesEstimated reading time: 3 minutes
There are several cases in the lifecycle of UCP when a node is actively transitioning from one state to another, such as when a new node is joining the cluster or during node promotion and demotion. In these cases, the current step of the transition will be reported by UCP as a node message. You can view the state of each individual node by following the same steps required to monitor cluster status.
UCP node states
The following table lists all possible node states that may be reported for a UCP node, their explanation, and the expected duration of a given step.
|Message||Description||Typical step duration|
|Completing node registration||Waiting for the node to appear in KV node inventory. This is expected to occur when a node first joins the UCP swarm.||5 - 30 seconds|
|The ucp-agent task is
|Unable to determine node state||The
|Node is being reconfigured||The
||1 - 60 seconds|
|Reconfiguration pending||The target node is expected to be a manager but the
||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. 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
||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