RKE2 server fails to start

Common reasons the RKE2 server fails to start in Automation Suite and how to diagnose them using server logs.

Description

The server fails to start. There are a few different reasons for RKE2 not starting properly, which are usually found in the logs.

Solution

To diagnose the issue, check the RKE2 server logs:

journalctl -u rke2-server

Cause: Too many learner members in cluster

Too many etcd servers are added to the cluster, and there are two learner nodes trying to be promoted. For more information, refer to Runtime reconfiguration.

To resolve this issue, perform one of the following:

1. Wait for the node to automatically become a full member. Under normal circumstances, this happens after enough time has passed.
2. If the issue persists, run an uninstall-reinstall cycle.

Cause: Networking problem

Ensure you have configured the machine to enable the necessary ports.