etcd报错panic: recovering backend from snapshot error: database snapshot file path error: snap: snapsh

最新推荐文章于 2026-02-27 07:35:06 发布

原创

最新推荐文章于 2026-02-27 07:35:06 发布 · 3k 阅读

本文探讨了VMware服务故障如何导致k8s集群中etcd数据丢失，详细记录了kube-apiserver容器的异常行为和etcd服务的报错。重点介绍了问题排查过程，包括日志分析、解决方案（如删除数据并设置定期备份），以及预防措施。

VMware死机导致etcd数据丢失，造成k8s无法启动

k8s api-server容器不断退出、重启

root@ubuntu:~# docker ps -a |grep kube-apiserver
726f7082259d        0eaa5e1d871a                                                            "kube-apiserver --ad…"   27 seconds ago      Exited (255) 7 seconds ago                                                                                                                                                                                            k8s_kube-apiserver_kube-apiserver-ubuntu_kube-system_19e46c52e07acaf9990e1b09ab162d3c_9
2db76b8b2d63        k8s.gcr.io/pause:3.1                                                    "/pause"                 28 seconds ago      Up 27 seconds                                                                                                                                                                                                         k8s_POD_kube-apiserver-ubuntu_kube-system_19e46c52e07acaf9990e1b09ab162d3c_5
4830897ad463        k8s.gcr.io/pause:3.1                                                    "/pause"                 28 minutes ago      Exited (0) 27 minutes ago                                                                                                                                                                                             k8s_POD_kube-apiserver-ubuntu_kube-system_19e46c52e07acaf9990e1b09ab162d3c_4
root@ubuntu:~# docker logs 726f7082259d
Flag --insecure-port has been deprecated, This flag will be removed in a future version.
I1231 07:42:24.387492       1 server.go:560] external host was not specified, using 192.168.253.129
I1231 07:42:24.387615       1 server.go:147] Version: v1.15.11
I1231 07:42:24.591143       1 plugins.go:158] Loaded 10 mutating admission controller(s) successfully in the following order: NamespaceLifecycle,LimitRanger,ServiceAccount,NodeRestriction,TaintNodesByCondition,Priority,DefaultTolerationSeconds,DefaultStorageClass,StorageObjectInUseProtection,MutatingAdmissionWebhook.
I1231 07:42:24.591165       1 plugins.go:161] Loaded 6 validating admission controller(s) successfully in the following order: LimitRanger,ServiceAccount,Priority,PersistentVolumeClaimResize,ValidatingAdmissionWebhook,ResourceQuota.
E1231 07:42:24.591500       1 prometheus.go:55] failed to register depth metric admission_quota_controller: duplicate metrics collector registration attempted
E1231 07:42:24.591536       1 prometheus.go:68] failed to register adds metric admission_quota_controller: duplicate metrics collector registration attempted
E1231 07:42:24.591547       1 promet