Is this a BUG REPORT or FEATURE REQUEST?: /kind bug What happened: kubelet.service fail to start up What you expected to happen: kubelet.service start up success How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: kubelet.service file kubelet.service config file Environment:
|
kubelet service fail to start up ,I dont konw how to resolve it , |
Is it a duplicate for #54541 ? |
I also have the same issue when the kubelet always show error status 1/FAILURE is there any way to trace what makes this error? or maybe is there any way to fix it? |
show logs related to kubelet use journalctl |
Nov 02 15:12:12 kubernetes-master kubelet[2313]: I1102 15:12:12.324007 2313 controller.go:114] kubelet config controller: starting controller Nov 02 15:12:12 kubernetes-master kubelet[2313]: I1102 15:12:12.323899 2313 feature_gate.go:156] feature gates: map[] Nov 02 15:12:12 kubernetes-master systemd[1]: Starting kubelet: The Kubernetes Node Agent... Nov 02 15:12:12 kubernetes-master systemd[1]: Started kubelet: The Kubernetes Node Agent. Nov 02 15:12:12 kubernetes-master systemd[1]: kubelet.service holdoff time over, scheduling restart. Nov 02 15:12:02 kubernetes-master systemd[1]: kubelet.service failed. Nov 02 15:12:02 kubernetes-master systemd[1]: Unit kubelet.service entered failed state. Nov 02 15:12:02 kubernetes-master systemd[1]: kubelet.service: main process exited, code=exited, status=1/FAILURE Nov 02 15:12:02 kubernetes-master kubelet[2308]: error: unable to load client CA file /etc/kubernetes/pki/ca.crt: open /etc/kubernetes/pki/ca.crt: no such file or directory Nov 02 15:12:02 kubernetes-master kubelet[2308]: I1102 15:12:02.076525 2308 controller.go:118] kubelet config controller: validating combination of defaults and flags Nov 02 15:12:02 kubernetes-master kubelet[2308]: I1102 15:12:02.076519 2308 controller.go:114] kubelet config controller: starting controller Nov 02 15:12:02 kubernetes-master kubelet[2308]: I1102 15:12:02.076409 2308 feature_gate.go:156] feature gates: map[] Nov 02 15:12:01 kubernetes-master systemd[1]: Starting kubelet: The Kubernetes Node Agent... Nov 02 15:12:01 kubernetes-master systemd[1]: Started kubelet: The Kubernetes Node Agent. Nov 02 15:12:01 kubernetes-master systemd[1]: kubelet.service holdoff time over, scheduling restart. Nov 02 15:11:51 kubernetes-master systemd[1]: kubelet.service failed. Nov 02 15:11:51 kubernetes-master systemd[1]: Unit kubelet.service entered failed state. Nov 02 15:11:51 kubernetes-master systemd[1]: kubelet.service: main process exited, code=exited, status=1/FAILURE Nov 02 15:11:51 kubernetes-master kubelet[2303]: error: unable to load client CA file /etc/kubernetes/pki/ca.crt: open /etc/kubernetes/pki/ca.crt: no such file or directory Nov 02 15:11:51 kubernetes-master kubelet[2303]: I1102 15:11:51.831530 2303 controller.go:118] kubelet config controller: validating combination of defaults and flags Nov 02 15:11:51 kubernetes-master kubelet[2303]: I1102 15:11:51.831519 2303 controller.go:114] kubelet config controller: starting controller Nov 02 15:11:51 kubernetes-master kubelet[2303]: I1102 15:11:51.831386 2303 feature_gate.go:156] feature gates: map[] |
please switchoff your swap memory i faced same problem and when i remove swap entry from my /etc/fstab file .then it worked in my case.also do swapoff |
@awesomemayank007 Yes, but it doesn't work. What should I do?Do I need to restart the server in VM? |
Nov 02 15:12:02 kubernetes-master kubelet[2308]: error: unable to load client CA file /etc/kubernetes/pki/ca.crt: open /etc/kubernetes/pki/ca.crt: no such file or directory ca missing ? |
#yum install -y kubelet kubeadm kubectl docker Jst try installing docker 1.12...iam not getting solution with docker 1.17ce.( i think its not supported with kubelet) Make swap off by #swapoff -a Now reset kubeadm by #kubeadm reset Now try #kudeadm init after that check #systemctl status kubelet it will be working |
I had the same issue, journalctl revealed:I ran: then restarted kubelet, all good. |
/close |
when i use journalctl,the log shows HVMOP_pagetable_dying not supported: [root@NKG1000136919 kubernetes]# journalctl -- Logs begin at Wed 2018-08-22 15:46:45 CST, end at Wed 2018-08-22 16:43:17 CST. -- Aug 22 15:46:45 localhost.localdomain systemd-journal[134]: Runtime journal is using 8.0M (max allowed 389.9M, trying to le Aug 22 15:46:45 localhost.localdomain kernel: Initializing cgroup subsys cpuset Aug 22 15:46:45 localhost.localdomain kernel: Initializing cgroup subsys cpu Aug 22 15:46:45 localhost.localdomain kernel: Initializing cgroup subsys cpuacct Aug 22 15:46:45 localhost.localdomain kernel: Linux version 3.10.0-693.el7.x86_64 ([email protected]) (gcc ve Aug 22 15:46:45 localhost.localdomain kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-3.10.0-693.el7.x86_64 root=UUID=fdb6f8 Aug 22 15:46:45 localhost.localdomain kernel: e820: BIOS-provided physical RAM map: Aug 22 15:46:45 localhost.localdomain kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009f3ff] usable Aug 22 15:46:45 localhost.localdomain kernel: BIOS-e820: [mem 0x000000000009f400-0x000000000009ffff] reserved Aug 22 15:46:45 localhost.localdomain kernel: BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved Aug 22 15:46:45 localhost.localdomain kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000dfffefff] usable Aug 22 15:46:45 localhost.localdomain kernel: BIOS-e820: [mem 0x00000000dffff000-0x00000000dfffffff] reserved Aug 22 15:46:45 localhost.localdomain kernel: BIOS-e820: [mem 0x00000000fc000000-0x00000000ffffffff] reserved Aug 22 15:46:45 localhost.localdomain kernel: BIOS-e820: [mem 0x0000000100000000-0x000000021f7fffff] usable Aug 22 15:46:45 localhost.localdomain kernel: NX (Execute Disable) protection: active Aug 22 15:46:45 localhost.localdomain kernel: SMBIOS 2.4 present. Aug 22 15:46:45 localhost.localdomain kernel: DMI: Xen HVM domU, BIOS 4.1.2_115-900.260_ 11/06/2015 Aug 22 15:46:45 localhost.localdomain kernel: Hypervisor detected: Xen HVM Aug 22 15:46:45 localhost.localdomain kernel: Xen version 4.1. Aug 22 15:46:45 localhost.localdomain kernel: Xen Platform PCI: I/O protocol version 1 Aug 22 15:46:45 localhost.localdomain kernel: Netfront and the Xen platform PCI driver have been compiled for this kernel: Aug 22 15:46:45 localhost.localdomain kernel: Blkfront and the Xen platform PCI driver have been compiled for this kernel: You might have to change the root device from /dev/hd[a-d] to /dev/xvd[a-d] in your root= kernel command line option Aug 22 15:46:45 localhost.localdomain kernel: HVMOP_pagetable_dying not supported Aug 22 15:46:45 localhost.localdomain kernel: e820: update [mem 0x00000000-0x00000fff] usable > reserved Aug 22 15:46:45 localhost.localdomain kernel: e820: remove [mem 0x000a0000-0x000fffff] usable Aug 22 15:46:45 localhost.localdomain kernel: e820: last_pfn = 0x21f800 max_arch_pfn = 0x400000000 Aug 22 15:46:45 localhost.localdomain kernel: MTRR default type: write-back Aug 22 15:46:45 localhost.localdomain kernel: MTRR fixed ranges enabled: Aug 22 15:46:45 localhost.localdomain kernel: 00000-9FFFF write-back Aug 22 15:46:45 localhost.localdomain kernel: A0000-BFFFF write-combining Aug 22 15:46:45 localhost.localdomain kernel: C0000-FFFFF write-back Aug 22 15:46:45 localhost.localdomain kernel: MTRR variable ranges enabled: Aug 22 15:46:45 localhost.localdomain kernel: 0 base 0000F0000000 mask 3FFFF8000000 uncachable Aug 22 15:46:45 localhost.localdomain kernel: 1 base 0000F8000000 mask 3FFFFC000000 uncachable anybody know the reason? |
the same question I have |
brilliant |
Thanks for your commented. |