环境信息:
RKE2 版本:
节点 CPU 架构，操作系统和版本：
集群配置:
1servers,3agent
问题描述:
service节点会莫名其妙的停止掉，container主进程停止
重现步骤:
- 安装 RKE2 的命令:
官方提供的一键脚本安装的，系统也是全新安装的ubuntu24
● rke2-server.service - Rancher Kubernetes Engine v2 (server)
Loaded: loaded (/usr/local/lib/systemd/system/rke2-server.service; enabled; preset: enabled)
Active: activating (start) since Mon 2026-06-01 01:30:24 UTC; 12s ago
Docs: https://github.com/rancher/rke2#readme
Process: 2436312 ExecCondition=/bin/sh -c if systemctl is-active --quiet rke2-agent.service; then echo “Error: rke2-agent is running!”; exit 1; fi (code=exited, status=0/SUCCESS)
Process: 2436314 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS)
Process: 2436317 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
Main PID: 2436319 (rke2)
Tasks: 183
Memory: 1.5G (peak: 4.2G)
CPU: 165ms
CGroup: /system.slice/rke2-server.service
├─ 5672 /var/lib/rancher/rke2/data/v1.35.5-rke2r1-a0d90cdcd0dc/bin/containerd-shim-runc-v2 -namespace k8s.io -id ac796f903055929fd45cae3b8c80ec8979f489ed9310288d3720556852b06138 -address /run/k3s/containerd/containerd.sock
├─ 5718 /var/lib/rancher/rke2/data/v1.35.5-rke2r1-a0d90cdcd0dc/bin/containerd-shim-runc-v2 -namespace k8s.io -id 07cfb0a1904d0d69f820eb8b47cb57bc9c00ae5fc3ed0f045c06bad6bd439926 -address /run/k3s/containerd/containerd.sock
├─ 5909 /var/lib/rancher/rke2/data/v1.35.5-rke2r1-a0d90cdcd0dc/bin/containerd-shim-runc-v2 -namespace k8s.io -id a90a5cf507ee00b9cf3dde38ef2d784781289101ec9e19d93c3071eb98ffbc9e -address /run/k3s/containerd/containerd.sock
├─ 6092 /var/lib/rancher/rke2/data/v1.35.5-rke2r1-a0d90cdcd0dc/bin/containerd-shim-runc-v2 -namespace k8s.io -id d1fc847eda6311a958ef8a4562b71a891bef46db5e2f895916b9ebdbe6e95df0 -address /run/k3s/containerd/containerd.sock
├─ 6167 /var/lib/rancher/rke2/data/v1.35.5-rke2r1-a0d90cdcd0dc/bin/containerd-shim-runc-v2 -namespace k8s.io -id abdfbb238633edbe9a08fed4513bd9cafbce720198d2244b14aee9abbca60b40 -address /run/k3s/containerd/containerd.sock
├─ 6451 /var/lib/rancher/rke2/data/v1.35.5-rke2r1-a0d90cdcd0dc/bin/containerd-shim-runc-v2 -namespace k8s.io -id 62168d2d9522b127b06b7d48c0c79959cd78f25af87ebdab86f3f85fc576c539 -address /run/k3s/containerd/containerd.sock
├─ 10090 /var/lib/rancher/rke2/data/v1.35.5-rke2r1-a0d90cdcd0dc/bin/containerd-shim-runc-v2 -namespace k8s.io -id 304eb10c7b95a58b99a784c9280113313e179368cb7f37d9ce13f7f8dd6a7df2 -address /run/k3s/containerd/containerd.sock
├─ 36685 /var/lib/rancher/rke2/data/v1.35.5-rke2r1-a0d90cdcd0dc/bin/containerd-shim-runc-v2 -namespace k8s.io -id bd7eb3d4ccd0f6dd8ae4561446f1435a4247437a0e28fc68ce2dab7581039774 -address /run/k3s/containerd/containerd.sock
├─ 36906 /var/lib/rancher/rke2/data/v1.35.5-rke2r1-a0d90cdcd0dc/bin/containerd-shim-runc-v2 -namespace k8s.io -id 03549110101f994293deb4b43a60b1fd2999682364fa27696681124d26011ce1 -address /run/k3s/containerd/containerd.sock
├─ 38269 /var/lib/rancher/rke2/data/v1.35.5-rke2r1-a0d90cdcd0dc/bin/containerd-shim-runc-v2 -namespace k8s.io -id 4024ab8584d37fd2f4cfb8341310f8b4b44fff750c3e958e2021f042160ddf45 -address /run/k3s/containerd/containerd.sock
├─ 38871 /var/lib/rancher/rke2/data/v1.35.5-rke2r1-a0d90cdcd0dc/bin/containerd-shim-runc-v2 -namespace k8s.io -id 142631528dae3ee2bc247dc7c347ee3c0d439704fcc2bfc243d1549bc99647d2 -address /run/k3s/containerd/containerd.sock
├─ 43790 /var/lib/rancher/rke2/data/v1.35.5-rke2r1-a0d90cdcd0dc/bin/containerd-shim-runc-v2 -namespace k8s.io -id aba4c476ac566ebe41235975633e2716095e4f3424aabd3d75658f34bc752533 -address /run/k3s/containerd/containerd.sock
├─ 50442 /var/lib/rancher/rke2/data/v1.35.5-rke2r1-a0d90cdcd0dc/bin/containerd-shim-runc-v2 -namespace k8s.io -id 10c2f17867f9467c2b051a4001920b115a4c61f5d6620f1e6ca9ce291cd5dc12 -address /run/k3s/containerd/containerd.sock
├─ 61908 /var/lib/rancher/rke2/data/v1.35.5-rke2r1-a0d90cdcd0dc/bin/containerd-shim-runc-v2 -namespace k8s.io -id 09fb077ed7d53ba67ad1f3f2c2d03412a1b452e98186b4bd2d845041dfaf24eb -address /run/k3s/containerd/containerd.sock
├─ 290632 /var/lib/rancher/rke2/data/v1.35.5-rke2r1-a0d90cdcd0dc/bin/containerd-shim-runc-v2 -namespace k8s.io -id baf8f7ddf3a0f257e155e73d675e03e7efc1a23e30b58b811564ced98c935946 -address /run/k3s/containerd/containerd.sock
└─2436319 “/usr/local/bin/rke2 server”
Jun 01 01:30:29 yc systemd[1]: rke2-server.service: Found left-over process 61908 (containerd-shim) in control group while starting unit. Ignoring.
Jun 01 01:30:29 yc systemd[1]: rke2-server.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jun 01 01:30:29 yc systemd[1]: rke2-server.service: Found left-over process 290632 (containerd-shim) in control group while starting unit. Ignoring.
Jun 01 01:30:29 yc systemd[1]: rke2-server.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Jun 01 01:30:29 yc rke2[2436319]: time=“2026-06-01T01:30:29Z” level=warning msg=“not running in CIS mode”
Jun 01 01:30:29 yc rke2[2436319]: time=“2026-06-01T01:30:29Z” level=info msg=“Applying Pod Security Admission Configuration”
Jun 01 01:30:29 yc rke2[2436319]: time=“2026-06-01T01:30:29Z” level=info msg=“Starting rke2 v1.35.5+rke2r1 (e28e7c1a0404f1e9bf36e8b7222d64aec6b7a004)”
Jun 01 01:30:29 yc rke2[2436319]: time=“2026-06-01T01:30:29Z” level=info msg=“Managed etcd cluster bootstrap already complete and initialized”
Jun 01 01:30:29 yc rke2[2436319]: time=“2026-06-01T01:30:29Z” level=info msg=“Reconciling bootstrap data between datastore and disk”
Jun 01 01:30:29 yc rke2[2436319]: time=“2026-06-01T01:30:29Z” level=info msg=“Opening etcd client connection with endpoints [https://127.0.0.1:2379]”