refined-gigabyte-18875
02/25/2025, 11:17 AMctr -a /run/k3s/containerd/containerd.sock
but it also result in context deadline exceeded. Does anyone know what might be the issue or how I could potentially fix it?hundreds-evening-84071
02/25/2025, 12:35 PMhundreds-evening-84071
02/25/2025, 12:36 PMrefined-gigabyte-18875
02/25/2025, 12:40 PMkubectl
to check some things because the master nodes are all dead.refined-gigabyte-18875
02/25/2025, 12:41 PMhundreds-evening-84071
02/25/2025, 12:44 PMcrictl
and etcdctl
https://gist.github.com/superseb/3b78f47989e0dbc1295486c186e944bf#on-the-etcd-host-itself
did you see alarm:NOSPACE
with etcd? journalctl -u rke2-server
refined-gigabyte-18875
02/25/2025, 12:46 PMdu -h
and I have more than sufficient space available on disk hmmrefined-gigabyte-18875
02/25/2025, 12:54 PMrke2 server --debug
, I saw like it was going to 127.0.0.1 and some port that is not 2379 or etcd kinda port number, then subsequently something like
"Failed to test data store connection: context deadline exceeded"
I tried to do a "cluster-reset" on one of the control plane node as well, but when I tried to use the latest snapshot for restoration, it failed midway (didn't got a good look at why) but not doing restoration would work, not sure if it's possibly a corrupted etcd.