API tools faq
paste
Advertisement
konstest

Untitled

konstest
Jun 28th, 2022
82
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.69 KB | None | 0 0
raw download clone embed print report
  1. root@master-01:/home/cm# kubeadm init
  2. W0629 07:33:17.121588 1589 version.go:103] could not fetch a Kubernetes version from the internet: unable to get URL "https://dl.k8s.io/release/stable-1.txt": Get "https://dl.k8s.io/release/stable-1.txt": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
  3. W0629 07:33:17.121677 1589 version.go:104] falling back to the local client version: v1.24.2
  4. [init] Using Kubernetes version: v1.24.2
  5. [preflight] Running pre-flight checks
  6. [WARNING SystemVerification]: missing optional cgroups: hugetlb
  7. [preflight] Pulling images required for setting up a Kubernetes cluster
  8. [preflight] This might take a minute or two, depending on the speed of your internet connection
  9. [preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
  10. [certs] Using certificateDir folder "/etc/kubernetes/pki"
  11. [certs] Generating "ca" certificate and key
  12. [certs] Generating "apiserver" certificate and key
  13. [certs] apiserver serving cert is signed for DNS names [kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local master-01.test-kube.my-company.ru] and IPs [10.96.0.1 10.0.176.45]
  14. [certs] Generating "apiserver-kubelet-client" certificate and key
  15. [certs] Generating "front-proxy-ca" certificate and key
  16. [certs] Generating "front-proxy-client" certificate and key
  17. [certs] Generating "etcd/ca" certificate and key
  18. [certs] Generating "etcd/server" certificate and key
  19. [certs] etcd/server serving cert is signed for DNS names [localhost master-01.test-kube.my-company.ru] and IPs [10.0.176.45 127.0.0.1 ::1]
  20. [certs] Generating "etcd/peer" certificate and key
  21. [certs] etcd/peer serving cert is signed for DNS names [localhost master-01.test-kube.my-company.ru] and IPs [10.0.176.45 127.0.0.1 ::1]
  22. [certs] Generating "etcd/healthcheck-client" certificate and key
  23. [certs] Generating "apiserver-etcd-client" certificate and key
  24. [certs] Generating "sa" key and public key
  25. [kubeconfig] Using kubeconfig folder "/etc/kubernetes"
  26. [kubeconfig] Writing "admin.conf" kubeconfig file
  27. [kubeconfig] Writing "kubelet.conf" kubeconfig file
  28. [kubeconfig] Writing "controller-manager.conf" kubeconfig file
  29. [kubeconfig] Writing "scheduler.conf" kubeconfig file
  30. [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
  31. [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
  32. [kubelet-start] Starting the kubelet
  33. [control-plane] Using manifest folder "/etc/kubernetes/manifests"
  34. [control-plane] Creating static Pod manifest for "kube-apiserver"
  35. [control-plane] Creating static Pod manifest for "kube-controller-manager"
  36. [control-plane] Creating static Pod manifest for "kube-scheduler"
  37. [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
  38. [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
  39. [kubelet-check] Initial timeout of 40s passed.
  40.  
  41. Unfortunately, an error has occurred:
  42. timed out waiting for the condition
  43.  
  44. This error is likely caused by:
  45. - The kubelet is not running
  46. - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
  47.  
  48. If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
  49. - 'systemctl status kubelet'
  50. - 'journalctl -xeu kubelet'
  51.  
  52. Additionally, a control plane component may have crashed or exited when started by the container runtime.
  53. To troubleshoot, list all containers using your preferred container runtimes CLI.
  54. Here is one example how you may list all running Kubernetes containers by using crictl:
  55. - 'crictl --runtime-endpoint unix:///var/run/containerd/containerd.sock ps -a | grep kube | grep -v pause'
  56. Once you have found the failing container, you can inspect its logs with:
  57. - 'crictl --runtime-endpoint unix:///var/run/containerd/containerd.sock logs CONTAINERID'
  58. error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
  59. To see the stack trace of this error execute with --v=5 or higher
  60. root@master-01:/home/cm# crictl --runtime-endpoint unix:///var/run/containerd/containerd.sock ps -a | grep kube | grep -v pause
  61. root@master-01:/home/cm# crictl --runtime-endpoint unix:///var/run/containerd/containerd.sock logs CONTAINERID
  62. E0629 07:43:07.220566 6841 remote_runtime.go:604] "ContainerStatus from runtime service failed" err="rpc error: code = NotFound desc = an error occurred when try to find container \"CONTAINERID\": not found" containerID="CONTAINERID"
  63. FATA[0000] rpc error: code = NotFound desc = an error occurred when try to find container "CONTAINERID": not found
  64.  
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!