Kubernetes - memcache.go:265] couldn't get current server API group list

Facing the error below on Ubuntu 22.04 on vagrant. Error showing after halting and powering up the vms again. Checking the journal logs and tested was just a matter to disable swap on ubuntu.

root@master:/etc/kubernetes# kubectl get pods
E1212 12:55:53.292062    1865 memcache.go:265] couldn't get current server API group list: Get "https://192.168.122.200:6443/api?timeout=32s": dial tcp 192.168.122.200:6443: connect: connection refused
E1212 12:55:53.292515    1865 memcache.go:265] couldn't get current server API group list: Get "https://192.168.122.200:6443/api?timeout=32s": dial tcp 192.168.122.200:6443: connect: connection refused
E1212 12:55:53.294534    1865 memcache.go:265] couldn't get current server API group list: Get "https://192.168.122.200:6443/api?timeout=32s": dial tcp 192.168.122.200:6443: connect: connection refused
E1212 12:55:53.295070    1865 memcache.go:265] couldn't get current server API group list: Get "https://192.168.122.200:6443/api?timeout=32s": dial tcp 192.168.122.200:6443: connect: connection refused
E1212 12:55:53.296371    1865 memcache.go:265] couldn't get current server API group list: Get "https://192.168.122.200:6443/api?timeout=32s": dial tcp 192.168.122.200:6443: connect: connection refused
The connection to the server 192.168.122.200:6443 was refused - did you specify the right host or port?
root@master:/etc/kubernetes# 
root@master:/etc/kubernetes# 
root@master:/etc/kubernetes# kubectl get pods
E1212 12:56:19.646982    1894 memcache.go:265] couldn't get current server API group list: Get "https://192.168.122.200:6443/api?timeout=32s": dial tcp 192.168.122.200:6443: connect: connection refused
E1212 12:56:19.648779    1894 memcache.go:265] couldn't get current server API group list: Get "https://192.168.122.200:6443/api?timeout=32s": dial tcp 192.168.122.200:6443: connect: connection refused
E1212 12:56:19.648987    1894 memcache.go:265] couldn't get current server API group list: Get "https://192.168.122.200:6443/api?timeout=32s": dial tcp 192.168.122.200:6443: connect: connection refused
E1212 12:56:19.650532    1894 memcache.go:265] couldn't get current server API group list: Get "https://192.168.122.200:6443/api?timeout=32s": dial tcp 192.168.122.200:6443: connect: connection refused
E1212 12:56:19.651599    1894 memcache.go:265] couldn't get current server API group list: Get "https://192.168.122.200:6443/api?timeout=32s": dial tcp 192.168.122.200:6443: connect: connection refused
The connection to the server 192.168.122.200:6443 was refused - did you specify the right host or port?
root@master:/etc/kubernetes# systemctl status kube-apiserver
Unit kube-apiserver.service could not be found.
root@master:/etc/kubernetes# journalctl -r
Dec 12 12:56:50 master systemd[1]: kubelet.service: Failed with result 'exit-code'.
Dec 12 12:56:50 master systemd[1]: kubelet.service: Main process exited, code=exited, status=1/FAILURE
Dec 12 12:56:50 master kubelet[1933]: E1212 12:56:50.910912    1933 run.go:74] "command failed" err="failed to run Kubelet: running with swap on is >
Dec 12 12:56:50 master kubelet[1933]: I1212 12:56:50.910829    1933 server.go:725] "--cgroups-per-qos enabled, but --cgroup-root was not specified. >
Dec 12 12:56:50 master kubelet[1933]: I1212 12:56:50.904363    1933 dynamic_cafile_content.go:157] "Starting controller" name="client-ca-bundle::/et>
Dec 12 12:56:50 master kubelet[1933]: I1212 12:56:50.903655    1933 certificate_store.go:130] Loading cert/key pair from "/var/lib/kubelet/pki/kubel>
Dec 12 12:56:50 master kubelet[1933]: I1212 12:56:50.902837    1933 server.go:895] "Client rotation is on, will bootstrap in background"
Dec 12 12:56:50 master kubelet[1933]: I1212 12:56:50.902693    1933 server.go:469] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
Dec 12 12:56:50 master kubelet[1933]: I1212 12:56:50.902555    1933 server.go:467] "Kubelet version" kubeletVersion="v1.28.2"
Dec 12 12:56:50 master kubelet[1933]: I1212 12:56:50.900275    1933 server.go:203] "--pod-infra-container-image will not be pruned by the image garb>
Dec 12 12:56:50 master kubelet[1933]: Flag --pod-infra-container-image has been deprecated, will be removed in a future release. Image garbage colle>
Dec 12 12:56:50 master kubelet[1933]: Flag --container-runtime-endpoint has been deprecated, This parameter should be set via the config file specif>
Dec 12 12:56:50 master systemd[1]: Started kubelet: The Kubernetes Node Agent.
Dec 12 12:56:50 master systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
Dec 12 12:56:50 master systemd[1]: kubelet.service: Scheduled restart job, restart counter is at 61.
Dec 12 12:56:40 master systemd[1]: kubelet.service: Failed with result 'exit-code'.
Dec 12 12:56:40 master systemd[1]: kubelet.service: Main process exited, code=exited, status=1/FAILURE
Dec 12 12:56:40 master kubelet[1923]: E1212 12:56:40.667501    1923 run.go:74] "command failed" err="failed to run Kubelet: running with swap on is >
Dec 12 12:56:40 master kubelet[1923]: I1212 12:56:40.667204    1923 server.go:725] "--cgroups-per-qos enabled, but --cgroup-root was not specified. >

Comentários

Postar um comentário

Postagens mais visitadas deste blog

Transformando o Linksys WRT54G2 V1 em bridge, repetidor

Imagem
Eu tenho aqui um linksys WRT54G2 V1, o modelo abaixo: infodepot.wikia.com Estava encostado em um canto devido eu ter comprado um Netgear WNR1000. Eis que preciso expandir minha rede wi-fi, assim com um roteador principal no meu quarto, queria deixar outro router na sala por exemplo e conectar algum outro computador por lá. Mas o firmware que vem nesse router é uma negação e não permite transforma-lo em um repetidor, bridge ou o que for, então precisei instalar um firmware customizado provido pelo dd-wrt.com, a vantagem desse firmware é que ele expande as funções para o seu roteador, depois de instalado pude transformar meu roteador em um cliente, que no caso apenas pega o sinal do roteador principal e passa para as portas ethernets como se fosse um hub, existe outra configuração para transforma-lo em um repetido, fazendo assim com  que o sinal wi-fi fique disponível a uma maior distância. Para entender melhor isso, visite esse endereço no fórum hardmod , que
Leia mais

Recuperando partições deletadas

Imagem
--> Há um tempo atrás tive um sério problema, ao tentar formatar meu hd e instalar o windows, acabei sem querer deletando minha partição onde estavam todos os meus dados importantes, nem preciso dizer que fiquei desesperado, mas nada que um pouco de conhecimento e um bom software não pudessem resolver, o que fiz então, usei um software chamado testdisk para recuperar a partição deletada. Antes de mostrar como eu fiz isso, vou explicar melhor alguns pontos chave, já que talvez quem esteja lendo esse texto não seja nenhum perito em informática, então é necessário saber algumas coisas para que se possa usar o software sem problemas. O HD Todos devem conhecer o bom e velho HD (Hard Disk): Agora vemos suas p artes internas: Bem, isso é só uma elucidação básica, se quiser saber mais detalhes, veja este artigo o InfoWester . Bom, mas o que precisamos saber aqui é como o TestDisk trabalha, basicamente ele recupera a tabela de partição que foi deletada (apaga
Leia mais

How to install YUM and other rpm packages on VIOs and AIX manually

[Download rpm.rte] Download the rpm.rte from ibm site and update it. https://ftp.software.ibm.com/aix/freeSoftware/aixtoolbox/INSTALLP/ppc/rpm.rte.4.9.1.3 installp -acgXYd rpm.rte or use smitty update_all [Download the yum_bundle.tar] This file have all the necessary packages to install yum in a AIX system. NOTE: is very import to update the rpm.rte first, if you not update it first you can have errors messages if you try to install yum. As part of the installation of the rpm.rte, it runs as well the updtvpkg command to update the rpm database that have reference for new libs on the system that are used when you try to install new packages. wget -c https://public.dhe.ibm.com/aix/freeSoftware/aixtoolbox/ezinstall/ppc/yum_bundle.tar try to install using the command rpm -Uvh *.rpm Sometimes the command will fail due readline and glib packages, you can exclude them, sometimes you will already have some packages installed, you can exclude them using: rpm -Uvh $(ls *
Leia mais