1. [root@ur-scm-worker07 ~]# 
    2. [root@ur-scm-worker07 ~]# journalctl -u kubelet -f
    3. -- Logs begin at Fri 2022-04-22 09:42:26 CST. --
    4. Jun 29 22:15:02 ur-scm-worker07 kubelet[1210]: E0629 22:15:02.241871    1210 manager.go:1123] Failed to create existing container: /kubepods/burstable/pod03bee203-c8ea-4f13-8fe4-a101a0052431/9b1fac199bccac14503c4a5b50e944e7518e398fa328f781d6d04d10e6abafce: failed to identify the read-write layer ID for container "9b1fac199bccac14503c4a5b50e944e7518e398fa328f781d6d04d10e6abafce". - open /var/lib/docker/image/overlay2/layerdb/mounts/9b1fac199bccac14503c4a5b50e944e7518e398fa328f781d6d04d10e6abafce/mount-id: no such file or directory
    5. Jun 29 22:15:02 ur-scm-worker07 kubelet[1210]: E0629 22:15:02.242908    1210 manager.go:1123] Failed to create existing container: /kubepods/burstable/podd44378b2-b999-4047-ac90-bf3ba7bdfa01/c4e34b6913ad34d93440d5c196b750f470fbe7764adc4e1d1ed4843f405b5b67: failed to identify the read-write layer ID for container "c4e34b6913ad34d93440d5c196b750f470fbe7764adc4e1d1ed4843f405b5b67". - open /var/lib/docker/image/overlay2/layerdb/mounts/c4e34b6913ad34d93440d5c196b750f470fbe7764adc4e1d1ed4843f405b5b67/mount-id: no such file or directory
    6. Jun 29 22:15:02 ur-scm-worker07 kubelet[1210]: E0629 22:15:02.243980    1210 manager.go:1123] Failed to create existing container: /kubepods/besteffort/pod6e243bad-4195-4a5e-939f-bdacbff25655/c635d355580499c635be83c715d21980b0388a74b8a909761f619d41fe539ddd: failed to identify the read-write layer ID for container "c635d355580499c635be83c715d21980b0388a74b8a909761f619d41fe539ddd". - open /var/lib/docker/image/overlay2/layerdb/mounts/c635d355580499c635be83c715d21980b0388a74b8a909761f619d41fe539ddd/mount-id: no such file or directory
    7. Jun 29 22:15:02 ur-scm-worker07 kubelet[1210]: E0629 22:15:02.244898    1210 manager.go:1123] Failed to create existing container: /kubepods/besteffort/pod6e243bad-4195-4a5e-939f-bdacbff25655/935cb1c4006577f187e468a10603e47d74a9f0e27b39e124f2a64676d714a6b3: failed to identify the read-write layer ID for container "935cb1c4006577f187e468a10603e47d74a9f0e27b39e124f2a64676d714a6b3". - open /var/lib/docker/image/overlay2/layerdb/mounts/935cb1c4006577f187e468a10603e47d74a9f0e27b39e124f2a64676d714a6b3/mount-id: no such file or directory
    8. Jun 29 22:15:02 ur-scm-worker07 kubelet[1210]: E0629 22:15:02.245969    1210 manager.go:1123] Failed to create existing container: /kubepods/besteffort/pod7ba7a3fc-4ae4-4b31-adec-44b7822abb1a/2d8a6d98eb8640de87dbaedaad3cbfab586847aa60b76e5d5a5e64fdf42345c6: failed to identify the read-write layer ID for container "2d8a6d98eb8640de87dbaedaad3cbfab586847aa60b76e5d5a5e64fdf42345c6". - open /var/lib/docker/image/overlay2/layerdb/mounts/2d8a6d98eb8640de87dbaedaad3cbfab586847aa60b76e5d5a5e64fdf42345c6/mount-id: no such file or directory
    9. Jun 29 22:15:02 ur-scm-worker07 kubelet[1210]: E0629 22:15:02.246907    1210 manager.go:1123] Failed to create existing container: /kubepods/burstable/pod03bee203-c8ea-4f13-8fe4-a101a0052431/6bade943ee8f16e2480be6dc911c7448ca60b90c9e1ecb76e2cafdb1b607dda1: failed to identify the read-write layer ID for container "6bade943ee8f16e2480be6dc911c7448ca60b90c9e1ecb76e2cafdb1b607dda1". - open /var/lib/docker/image/overlay2/layerdb/mounts/6bade943ee8f16e2480be6dc911c7448ca60b90c9e1ecb76e2cafdb1b607dda1/mount-id: no such file or directory
    10. Jun 29 22:15:02 ur-scm-worker07 kubelet[1210]: E0629 22:15:02.247808    1210 manager.go:1123] Failed to create existing container: /kubepods/burstable/pod74818b9f-62cd-49f0-a844-bcc37f10fc19/4654c57975d21b1b9c049d72bb7bbc4ebe699a900acc66e98544a6e4fe7fa7dd: failed to identify the read-write layer ID for container "4654c57975d21b1b9c049d72bb7bbc4ebe699a900acc66e98544a6e4fe7fa7dd". - open /var/lib/docker/image/overlay2/layerdb/mounts/4654c57975d21b1b9c049d72bb7bbc4ebe699a900acc66e98544a6e4fe7fa7dd/mount-id: no such file or directory
    11. Jun 29 22:15:02 ur-scm-worker07 kubelet[1210]: E0629 22:15:02.249149    1210 manager.go:1123] Failed to create existing container: /kubepods/burstable/pod74818b9f-62cd-49f0-a844-bcc37f10fc19/39e1aba62e1cb94f08b4ad90a1ae3000210ff5d047ad1ce9780c8c4404c5a853: failed to identify the read-write layer ID for container "39e1aba62e1cb94f08b4ad90a1ae3000210ff5d047ad1ce9780c8c4404c5a853". - open /var/lib/docker/image/overlay2/layerdb/mounts/39e1aba62e1cb94f08b4ad90a1ae3000210ff5d047ad1ce9780c8c4404c5a853/mount-id: no such file or directory
    12. Jun 29 22:15:02 ur-scm-worker07 kubelet[1210]: E0629 22:15:02.250327    1210 manager.go:1123] Failed to create existing container: /kubepods/burstable/podd44378b2-b999-4047-ac90-bf3ba7bdfa01/4cd3aaef285c94443e660650af59726bb037d9af7359cc1540df4e2f5fee0d34: failed to identify the read-write layer ID for container "4cd3aaef285c94443e660650af59726bb037d9af7359cc1540df4e2f5fee0d34". - open /var/lib/docker/image/overlay2/layerdb/mounts/4cd3aaef285c94443e660650af59726bb037d9af7359cc1540df4e2f5fee0d34/mount-id: no such file or directory
    13. Jun 29 22:15:02 ur-scm-worker07 kubelet[1210]: E0629 22:15:02.655276    1210 summary_sys_containers.go:47] Failed to get system container stats for "/system.slice/docker.service": failed to get cgroup stats for "/system.slice/docker.service": failed to get container info for "/system.slice/docker.service": unknown container "/system.slice/docker.service"
    14. Jun 29 22:15:14 ur-scm-worker07 kubelet[1210]: E0629 22:15:14.107802    1210 summary_sys_containers.go:47] Failed to get system container stats for "/system.slice/docker.service": failed to get cgroup stats for "/system.slice/docker.service": failed to get container info for "/system.slice/docker.service": unknown container "/system.slice/docker.service"
    15. ^C
    16. [root@ur-scm-worker07 ~]#
    1. Jun 30 16:16:01 ur-scm-worker05 kubelet[1990]: I0630 16:16:01.780009    1990 reconciler.go:319] Volume detached for volume "run" (UniqueName: "kubernetes.io/configmap/63475bc1-1844-4a7f-a99f-bf117188f0f7-run") on node "ur-scm-worker05" DevicePath ""
    2. Jun 30 20:24:45 ur-scm-worker05 kubelet[1990]: E0630 20:24:45.256871    1990 server.go:265] Unable to authenticate the request due to an error: context canceled
    3. Jun 30 20:24:46 ur-scm-worker05 kubelet[1990]: E0630 20:24:45.452383    1990 server.go:265] Unable to authenticate the request due to an error: context canceled
    4. Jun 30 20:24:46 ur-scm-worker05 kubelet[1990]: E0630 20:24:45.452399    1990 server.go:265] Unable to authenticate the request due to an error: context canceled
    5. Jun 30 20:24:47 ur-scm-worker05 kubelet[1990]: E0630 20:24:47.225179    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    6. Jun 30 20:24:47 ur-scm-worker05 kubelet[1990]: E0630 20:24:47.426493    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    7. Jun 30 20:24:47 ur-scm-worker05 kubelet[1990]: E0630 20:24:47.628646    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    8. Jul 01 00:45:10 ur-scm-worker05 kubelet[1990]: E0701 00:45:10.821482    1990 handler.go:317] Error writing response: client disconnected
    9. Jul 01 03:16:13 ur-scm-worker05 kubelet[1990]: E0701 03:16:13.523544    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    10. Jul 01 03:16:13 ur-scm-worker05 kubelet[1990]: E0701 03:16:13.883381    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    11. Jul 01 03:16:14 ur-scm-worker05 kubelet[1990]: E0701 03:16:14.178796    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    12. Jul 01 03:16:14 ur-scm-worker05 kubelet[1990]: E0701 03:16:14.480089    1990 handler.go:317] Error writing response: http2: stream closed
    13. Jul 01 03:16:14 ur-scm-worker05 kubelet[1990]: E0701 03:16:14.481112    1990 handler.go:317] Error writing response: client disconnected
    14. Jul 01 03:16:14 ur-scm-worker05 kubelet[1990]: E0701 03:16:14.581989    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    15. Jul 01 03:26:53 ur-scm-worker05 kubelet[1990]: E0701 03:26:53.005078    1990 server.go:265] Unable to authenticate the request due to an error: context canceled
    16. Jul 01 03:26:53 ur-scm-worker05 kubelet[1990]: E0701 03:26:53.060336    1990 server.go:265] Unable to authenticate the request due to an error: context canceled
    17. Jul 01 03:26:53 ur-scm-worker05 kubelet[1990]: E0701 03:26:53.385038    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    18. Jul 01 03:26:53 ur-scm-worker05 kubelet[1990]: E0701 03:26:53.504881    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    19. Jul 01 03:26:53 ur-scm-worker05 kubelet[1990]: E0701 03:26:53.819291    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    20. Jul 01 03:26:54 ur-scm-worker05 kubelet[1990]: E0701 03:26:54.242199    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    21. Jul 01 04:27:52 ur-scm-worker05 kubelet[1990]: E0701 04:27:52.243198    1990 server.go:265] Unable to authenticate the request due to an error: context canceled
    22. Jul 01 07:25:37 ur-scm-worker05 kubelet[1990]: E0701 07:25:36.822866    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    23. Jul 01 07:25:38 ur-scm-worker05 kubelet[1990]: E0701 07:25:37.033647    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    24. Jul 01 07:25:38 ur-scm-worker05 kubelet[1990]: E0701 07:25:37.266097    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    25. Jul 01 07:25:38 ur-scm-worker05 kubelet[1990]: E0701 07:25:37.666428    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    26. Jul 01 07:25:38 ur-scm-worker05 kubelet[1990]: E0701 07:25:38.482150    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    27. Jul 01 09:13:51 ur-scm-worker05 kubelet[1990]: E0701 09:13:50.985256    1990 server.go:265] Unable to authenticate the request due to an error: context canceled
    28. Jul 01 09:13:51 ur-scm-worker05 kubelet[1990]: E0701 09:13:51.257720    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    29. Jul 01 09:13:51 ur-scm-worker05 kubelet[1990]: E0701 09:13:51.359044    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    30. Jul 01 09:13:51 ur-scm-worker05 kubelet[1990]: E0701 09:13:51.608091    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    31. Jul 01 09:35:50 ur-scm-worker05 kubelet[1990]: E0701 09:35:50.420885    1990 server.go:265] Unable to authenticate the request due to an error: context canceled
    32. Jul 01 09:35:50 ur-scm-worker05 kubelet[1990]: E0701 09:35:50.411202    1990 controller.go:178] failed to update node lease, error: Put "https://by-urk8s.ur.com.cn:6443/apis/coordination.k8s.io/v1/namespaces/kube-node-lease/leases/ur-scm-worker05?timeout=10s": context 
    33. Jul 01 09:35:50 ur-scm-worker05 kubelet[1990]: E0701 09:35:50.459565    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down
    34. Jul 01 09:35:50 ur-scm-worker05 kubelet[1990]: I0701 09:35:50.508937    1990 trace.go:205] Trace[1782374722]: "iptables Monitor CANARY check" (01-Jul-2022 09:35:34.545) (total time: 15914ms):
    35. Jul 01 09:35:50 ur-scm-worker05 kubelet[1990]: Trace[1782374722]: [15.914508618s] [15.914508618s] END
    36. Jul 01 09:35:50 ur-scm-worker05 kubelet[1990]: E0701 09:35:50.559971    1990 kubelet.go:1799] skipping pod synchronization - container runtime is down