This message was deleted.
# rke2
a
This message was deleted.
r
The container for kube-apiserver should get installed with the RPM or tar file, so I'd use the uninstall script that comes with it and try the install again.
c
that… is not how that works.
You’ve got the etcd pod started, the apiserver pod should be started soon after. If you see it get stuck waiting for the kube-apiserver container to be created, I would take a look at the logs under /var/log/pods to see if there are any errors.
r
Ah, so container not found just means "not running" rather than "not present." My bad on error message interpetation.
c
it essentially means there is no container matching that name in the
crictl ps
output
👍 1
j
I found no error in the /var/log/pods
2023-04-17T205426.138048682Z stderr F {"level":"info","ts":"2023-04-17T205426.137Z","caller":"embed/etcd.go:308","msg":"starting an etcd server","etcd-version":"3.5.4","git-sha":"Not provided (use ./build instead of go build)","go-version":"go1.16.10b7","go-os":"linux","go-arch":"amd64","max-cpu-set":1,"max-cpu-available":1,"member-initialized":false,"name":"rke2-a4831e51","data-dir":"/var/lib/rancher/rke2/server/db/etcd","wal-dir":"","wal-dir-dedicated":"","member-dir":"/var/lib/rancher/rke2/server/db/etcd/member","force-new-cluster":false,"heartbeat-interval":"500ms","election-timeout":"5s","initial-election-tick-advance":true,"snapshot-count":10000,"snapshot-catchup-entries":5000,"initial-advertise-peer-urls":["https://192.168.1.89:2380"],"listen-peer-urls":["https://127.0.0.1:2380","https://192.168.1.89:2380"],"advertise-client-urls":["https://192.168.1.89:2379"],"listen-client-urls":["https://127.0.0.1:2379","https://192.168.1.89:2379"],"listen-metrics-urls":["http://127.0.0.1:2381"],"cors":["*"],"host-whitelist":["*"],"initial-cluster":"rke2-a4831e51=https://192.168.1.89:2380","initial-cluster-state":"new","initial-cluster-token":"etcd-cluster","quota-size-bytes":2147483648,"pre-vote":true,"initial-corrupt-check":true,"corrupt-check-time-interval":"0s","auto-compaction-mode":"","auto-compaction-retention":"0s","auto-compaction-interval":"0s","discovery-url":"","discovery-proxy":"","downgrade-check-interval":"5s"}
c
check the containerd.log then as well. There’s something preventing the apiserver static pod from starting.
j
nothing for apiserver
c
please attach the complete containerd.log and kubelet.log
j
Here you go
c
that is the etcd pod log and looks fine, can you get the kubelet and containerd logs?
j
where do I find them
c
Copy code
/var/lib/rancher/rke2/agent/logs/kubelet.log
/var/lib/rancher/rke2/agent/containerd/containerd.log
attach please (as above), don’t copy-paste
You don’t have enough memory.
Copy code
I0418 18:42:09.510576   14564 predicate.go:103] "Failed to admit pod, unexpected error while attempting to recover from admission failure" pod="kube-system/kube-apiserver-rke2" err="preemption: error finding a set of pods to preempt: no set of running pods found to reclaim resources: [(res: memory, q: 586317824), ]
Please ensure that your node meets the minimum system requirements: https://docs.rke2.io/install/requirements#linuxwindows
How much memory do you have on this node, like 1GB? It doesn’t have enough to run more than just the etcd pod.
j
Thanks Adding the memory was the ticket
1430 Views