Hi, I have a k8s cluster managed by harvester, the cluster only has 1 node. I had to reboot the machine and would like to start the cluster again. I run the command

systemctl start rancher-system-agent.service && systemctl start rke2-agent.service && systemctl start rke2-server.service

but

rke2-agent

fails to start journalctl says:

Apr 28 12:03:30 nid003204 systemd[1]: rke2-agent.service: Failed with result 'exit-code'.
Apr 28 12:03:30 nid003204 systemd[1]: Failed to start Rancher Kubernetes Engine v2 (agent).
Apr 28 12:03:36 nid003204 systemd[1]: rke2-agent.service: Scheduled restart job, restart counter is at 42.
Apr 28 12:03:36 nid003204 systemd[1]: Stopped Rancher Kubernetes Engine v2 (agent).
Apr 28 12:03:36 nid003204 systemd[1]: Starting Rancher Kubernetes Engine v2 (agent)...
Apr 28 12:03:36 nid003204 sh[134363]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
Apr 28 12:03:36 nid003204 sh[134364]: Failed to get unit file state for nm-cloud-setup.service: No such file or directory
Apr 28 12:03:36 nid003204 rke2[134367]: time="2023-04-28T12:03:36+02:00" level=warning msg="Unknown flag --agent-token found in config.yaml, skipping\n"
Apr 28 12:03:36 nid003204 rke2[134367]: time="2023-04-28T12:03:36+02:00" level=warning msg="Unknown flag --cni found in config.yaml, skipping\n"
Apr 28 12:03:36 nid003204 rke2[134367]: time="2023-04-28T12:03:36+02:00" level=warning msg="Unknown flag --disable found in config.yaml, skipping\n"
Apr 28 12:03:36 nid003204 rke2[134367]: time="2023-04-28T12:03:36+02:00" level=warning msg="Unknown flag --disable-kube-proxy found in config.yaml, skipping\n"
Apr 28 12:03:36 nid003204 rke2[134367]: time="2023-04-28T12:03:36+02:00" level=warning msg="Unknown flag --etcd-expose-metrics found in config.yaml, skipping\n"
Apr 28 12:03:36 nid003204 rke2[134367]: time="2023-04-28T12:03:36+02:00" level=warning msg="Unknown flag --etcd-snapshot-retention found in config.yaml, skipping\n"
Apr 28 12:03:36 nid003204 rke2[134367]: time="2023-04-28T12:03:36+02:00" level=warning msg="Unknown flag --etcd-snapshot-schedule-cron found in config.yaml, skipping\n"
Apr 28 12:03:36 nid003204 rke2[134367]: time="2023-04-28T12:03:36+02:00" level=warning msg="Unknown flag --kube-controller-manager-arg found in config.yaml, skipping\n"
Apr 28 12:03:36 nid003204 rke2[134367]: time="2023-04-28T12:03:36+02:00" level=warning msg="Unknown flag --kube-controller-manager-arg found in config.yaml, skipping\n"
Apr 28 12:03:36 nid003204 rke2[134367]: time="2023-04-28T12:03:36+02:00" level=warning msg="Unknown flag --kube-scheduler-arg found in config.yaml, skipping\n"
Apr 28 12:03:36 nid003204 rke2[134367]: time="2023-04-28T12:03:36+02:00" level=warning msg="Unknown flag --kube-scheduler-arg found in config.yaml, skipping\n"
Apr 28 12:03:36 nid003204 rke2[134367]: time="2023-04-28T12:03:36+02:00" level=warning msg="not running in CIS mode"
Apr 28 12:03:36 nid003204 rke2[134367]: time="2023-04-28T12:03:36+02:00" level=fatal msg="--server is required"
Apr 28 12:03:36 nid003204 systemd[1]: rke2-agent.service: Main process exited, code=exited, status=1/FAILURE
Apr 28 12:03:36 nid003204 systemd[1]: rke2-agent.service: Failed with result 'exit-code'.
Apr 28 12:03:36 nid003204 systemd[1]: Failed to start Rancher Kubernetes Engine v2 (agent).

Any idea?

You can't run the agent and the server on the same node, a node can only be one or the other. Don't start both of the services.

why not?

Because it doesn't work that way