API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Dec 1st, 2021
113
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 179.38 KB | None | 0 0
raw download clone embed print report
  1. -- Logs begin at Sun 2021-11-28 18:39:45 UTC, end at Thu 2021-12-02 03:15:42 UTC. --
  2. Dec 02 03:15:36 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  3. Dec 02 03:15:36 k8s-node0 systemd[1]: containerd.service: Found left-over process 25412 (envoy) in control group while starting unit. Ignoring.
  4. Dec 02 03:15:36 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  5. Dec 02 03:15:36 k8s-node0 systemd[1]: containerd.service: Found left-over process 451726 (pause) in control group while starting unit. Ignoring.
  6. Dec 02 03:15:36 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  7. Dec 02 03:15:36 k8s-node0 systemd[1]: containerd.service: Found left-over process 452109 (pause) in control group while starting unit. Ignoring.
  8. Dec 02 03:15:36 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  9. Dec 02 03:15:36 k8s-node0 systemd[1]: containerd.service: Found left-over process 452295 (pause) in control group while starting unit. Ignoring.
  10. Dec 02 03:15:36 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  11. Dec 02 03:15:36 k8s-node0 systemd[1]: containerd.service: Found left-over process 452280 (pause) in control group while starting unit. Ignoring.
  12. Dec 02 03:15:36 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  13. Dec 02 03:15:36 k8s-node0 systemd[1]: containerd.service: Found left-over process 452272 (tini) in control group while starting unit. Ignoring.
  14. Dec 02 03:15:36 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  15. Dec 02 03:15:36 k8s-node0 systemd[1]: containerd.service: Found left-over process 452375 (toolbox.sh) in control group while starting unit. Ignoring.
  16. Dec 02 03:15:36 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  17. Dec 02 03:15:36 k8s-node0 systemd[1]: containerd.service: Found left-over process 2179664 (sleep) in control group while starting unit. Ignoring.
  18. Dec 02 03:15:36 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  19. Dec 02 03:15:36 k8s-node0 systemd[1]: containerd.service: Found left-over process 452642 (ceph-mds) in control group while starting unit. Ignoring.
  20. Dec 02 03:15:36 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  21. Dec 02 03:15:36 k8s-node0 systemd[1]: containerd.service: Found left-over process 453022 (ceph-mds) in control group while starting unit. Ignoring.
  22. Dec 02 03:15:36 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  23. Dec 02 03:15:36 k8s-node0 systemd[1]: containerd.service: Found left-over process 453017 (ceph-mgr) in control group while starting unit. Ignoring.
  24. Dec 02 03:15:36 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  25. Dec 02 03:15:36 k8s-node0 systemd[1]: containerd.service: Found left-over process 455348 (pause) in control group while starting unit. Ignoring.
  26. Dec 02 03:15:36 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  27. Dec 02 03:15:36 k8s-node0 systemd[1]: containerd.service: Found left-over process 455791 (ceph-crash) in control group while starting unit. Ignoring.
  28. Dec 02 03:15:36 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  29. Dec 02 03:15:36 k8s-node0 containerd[2179737]: containerd: invalid disabled plugin URI "restart" expect io.containerd.x.vx
  30. Dec 02 03:15:36 k8s-node0 systemd[1]: containerd.service: Main process exited, code=exited, status=1/FAILURE
  31. -- Subject: Unit process exited
  32. -- Defined-By: systemd
  33. -- Support: http://www.ubuntu.com/support
  34. --
  35. -- An ExecStart= process belonging to unit containerd.service has exited.
  36. --
  37. -- The process' exit code is 'exited' and its exit status is 1.
  38. Dec 02 03:15:36 k8s-node0 systemd[1]: containerd.service: Failed with result 'exit-code'.
  39. -- Subject: Unit failed
  40. -- Defined-By: systemd
  41. -- Support: http://www.ubuntu.com/support
  42. --
  43. -- The unit containerd.service has entered the 'failed' state with result 'exit-code'.
  44. Dec 02 03:15:36 k8s-node0 systemd[1]: Failed to start containerd container runtime.
  45. -- Subject: A start job for unit containerd.service has failed
  46. -- Defined-By: systemd
  47. -- Support: http://www.ubuntu.com/support
  48. --
  49. -- A start job for unit containerd.service has finished with a failure.
  50. --
  51. -- The job identifier is 11784 and the job result is failed.
  52. Dec 02 03:15:36 k8s-node0 kubelet[4427]: E1202 03:15:36.142333 4427 remote_runtime.go:207] "ListPodSandbox with filter from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" filter="nil"
  53. Dec 02 03:15:36 k8s-node0 kubelet[4427]: E1202 03:15:36.142411 4427 kuberuntime_sandbox.go:223] "Failed to list pod sandboxes" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  54. Dec 02 03:15:36 k8s-node0 kubelet[4427]: E1202 03:15:36.142454 4427 generic.go:205] "GenericPLEG: Unable to retrieve pods" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  55. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.143553 4427 remote_runtime.go:207] "ListPodSandbox with filter from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" filter="nil"
  56. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.143657 4427 kuberuntime_sandbox.go:223] "Failed to list pod sandboxes" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  57. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.143735 4427 generic.go:205] "GenericPLEG: Unable to retrieve pods" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  58. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.264425 4427 remote_runtime.go:207] "ListPodSandbox with filter from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" filter="&PodSandboxFilter{Id:,State:&PodSandboxStateValue{State:SANDBOX_READY,},LabelSelector:map[string]string{},}"
  59. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.264474 4427 kuberuntime_sandbox.go:223] "Failed to list pod sandboxes" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  60. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.264494 4427 kubelet_pods.go:1107] "Error listing containers" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  61. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.264516 4427 kubelet.go:2011] "Failed cleaning pods" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  62. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.371204 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="aee3fa192c35354fa1b239bde371f7d00f7b6f52cf58af2650b796668ba54937" cmd=[/bin/sh -c exec pg_isready -U "admin" -d "dbname=postgres" -h 127.0.0.1 -p 5432]
  63. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.371206 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="aee3fa192c35354fa1b239bde371f7d00f7b6f52cf58af2650b796668ba54937" cmd=[/bin/sh -c -e exec pg_isready -U "admin" -d "dbname=postgres sslcert=/opt/bitnami/postgresql/certs/tls.crt sslkey=/opt/bitnami/postgresql/certs/tls.key" -h 127.0.0.1 -p 5432
  64. Dec 02 03:15:37 k8s-node0 kubelet[4427]: [ -f /opt/bitnami/postgresql/tmp/.initialized ] || [ -f /bitnami/postgresql/.initialized ]
  65. Dec 02 03:15:37 k8s-node0 kubelet[4427]: ]
  66. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.371437 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="aee3fa192c35354fa1b239bde371f7d00f7b6f52cf58af2650b796668ba54937" cmd=[/bin/sh -c -e exec pg_isready -U "admin" -d "dbname=postgres sslcert=/opt/bitnami/postgresql/certs/tls.crt sslkey=/opt/bitnami/postgresql/certs/tls.key" -h 127.0.0.1 -p 5432
  67. Dec 02 03:15:37 k8s-node0 kubelet[4427]: [ -f /opt/bitnami/postgresql/tmp/.initialized ] || [ -f /bitnami/postgresql/.initialized ]
  68. Dec 02 03:15:37 k8s-node0 kubelet[4427]: ]
  69. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.371330 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="aee3fa192c35354fa1b239bde371f7d00f7b6f52cf58af2650b796668ba54937" cmd=[/bin/sh -c exec pg_isready -U "admin" -d "dbname=postgres" -h 127.0.0.1 -p 5432]
  70. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.371514 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="aee3fa192c35354fa1b239bde371f7d00f7b6f52cf58af2650b796668ba54937" cmd=[/bin/sh -c -e exec pg_isready -U "admin" -d "dbname=postgres sslcert=/opt/bitnami/postgresql/certs/tls.crt sslkey=/opt/bitnami/postgresql/certs/tls.key" -h 127.0.0.1 -p 5432
  71. Dec 02 03:15:37 k8s-node0 kubelet[4427]: [ -f /opt/bitnami/postgresql/tmp/.initialized ] || [ -f /bitnami/postgresql/.initialized ]
  72. Dec 02 03:15:37 k8s-node0 kubelet[4427]: ]
  73. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.371577 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Readiness" pod="postgresql-services/postgresql-shared-read-0" podUID=a68b47fe-3728-401d-bde6-1b79153dacba containerName="postgresql-shared"
  74. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.371631 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="aee3fa192c35354fa1b239bde371f7d00f7b6f52cf58af2650b796668ba54937" cmd=[/bin/sh -c exec pg_isready -U "admin" -d "dbname=postgres" -h 127.0.0.1 -p 5432]
  75. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.371705 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Liveness" pod="postgresql-services/postgresql-shared-read-0" podUID=a68b47fe-3728-401d-bde6-1b79153dacba containerName="postgresql-shared"
  76. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.483211 4427 remote_runtime.go:314] "ListContainers with filter from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" filter="&ContainerFilter{Id:,State:nil,PodSandboxId:,LabelSelector:map[string]string{},}"
  77. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.483273 4427 container_log_manager.go:183] "Failed to rotate container logs" err="failed to list containers: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  78. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.489673 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="d96d3685e507861ee9f2d3c82d27d787318feb5adb0c91ac932fe03ac75ec123" cmd=[sh -c /health/ping_readiness_local.sh 1]
  79. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.489747 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="d96d3685e507861ee9f2d3c82d27d787318feb5adb0c91ac932fe03ac75ec123" cmd=[sh -c /health/ping_liveness_local.sh 5]
  80. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.489776 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="d96d3685e507861ee9f2d3c82d27d787318feb5adb0c91ac932fe03ac75ec123" cmd=[sh -c /health/ping_readiness_local.sh 1]
  81. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.489840 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="d96d3685e507861ee9f2d3c82d27d787318feb5adb0c91ac932fe03ac75ec123" cmd=[sh -c /health/ping_liveness_local.sh 5]
  82. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.489908 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="d96d3685e507861ee9f2d3c82d27d787318feb5adb0c91ac932fe03ac75ec123" cmd=[sh -c /health/ping_liveness_local.sh 5]
  83. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.489960 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Liveness" pod="harbor-services/harbor-redis-master-0" podUID=f0893ff1-3aad-4f34-8663-49172688d6bf containerName="redis"
  84. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.489842 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="d96d3685e507861ee9f2d3c82d27d787318feb5adb0c91ac932fe03ac75ec123" cmd=[sh -c /health/ping_readiness_local.sh 1]
  85. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.490065 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Readiness" pod="harbor-services/harbor-redis-master-0" podUID=f0893ff1-3aad-4f34-8663-49172688d6bf containerName="redis"
  86. Dec 02 03:15:37 k8s-node0 kubelet[4427]: W1202 03:15:37.563347 4427 clientconn.go:1223] grpc: addrConn.createTransport failed to connect to {unix:///run/containerd/containerd.sock <nil> 0 <nil>}. Err :connection error: desc = "transport: Error while dialing dial unix:///run/containerd/containerd.sock: timeout". Reconnecting...
  87. Dec 02 03:15:37 k8s-node0 kubelet[4427]: I1202 03:15:37.563466 4427 balancer_conn_wrappers.go:78] pickfirstBalancer: HandleSubConnStateChange: 0xc000b96470, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing dial unix:///run/containerd/containerd.sock: timeout"}
  88. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.719337 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="8b1d841e6a917ff89962fa1d9b7d941bfb3144fd84e481032d7420c048118288" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.14.asok status]
  89. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.719452 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="8b1d841e6a917ff89962fa1d9b7d941bfb3144fd84e481032d7420c048118288" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.14.asok status]
  90. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.719530 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="8b1d841e6a917ff89962fa1d9b7d941bfb3144fd84e481032d7420c048118288" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.14.asok status]
  91. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.719574 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Liveness" pod="rook-ceph/rook-ceph-osd-14-564fdc5d45-9b68k" podUID=af28f90f-c8bf-459f-bca2-183b742b7d57 containerName="osd"
  92. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.720357 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="01db857c29696ae7f4d88882a169fb7e16ac0ec44251494922de95e30201f277" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.7.asok status]
  93. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.720456 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="01db857c29696ae7f4d88882a169fb7e16ac0ec44251494922de95e30201f277" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.7.asok status]
  94. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.720531 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="01db857c29696ae7f4d88882a169fb7e16ac0ec44251494922de95e30201f277" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.7.asok status]
  95. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.720578 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Liveness" pod="rook-ceph/rook-ceph-osd-7-6b556d5f5f-5zdjk" podUID=3cb24595-c6e0-4437-b812-bfd57fde1cfa containerName="osd"
  96. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.721599 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="78e527cc92b0c4af583ec68bfd2b62c05ca8cb395e582084e8329ac2a9dad45f" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.9.asok status]
  97. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.721701 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="78e527cc92b0c4af583ec68bfd2b62c05ca8cb395e582084e8329ac2a9dad45f" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.9.asok status]
  98. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.721779 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="78e527cc92b0c4af583ec68bfd2b62c05ca8cb395e582084e8329ac2a9dad45f" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.9.asok status]
  99. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.721824 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Liveness" pod="rook-ceph/rook-ceph-osd-9-7d8774b9f9-ccbdx" podUID=6b621121-21c8-4831-817b-0605ae4ece0a containerName="osd"
  100. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.722770 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="c1a33f516cd7e6ab53cb69fbaa199fe24d823e4f27a7e854398efa3a8d2aa27c" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.11.asok status]
  101. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.722906 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="c1a33f516cd7e6ab53cb69fbaa199fe24d823e4f27a7e854398efa3a8d2aa27c" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.11.asok status]
  102. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.722993 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="c1a33f516cd7e6ab53cb69fbaa199fe24d823e4f27a7e854398efa3a8d2aa27c" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.11.asok status]
  103. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.723041 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Liveness" pod="rook-ceph/rook-ceph-osd-11-5f6b9647b7-5frn5" podUID=33b71cf7-7b4d-4404-a6bc-fa62ec7e0518 containerName="osd"
  104. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.729042 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="75b3cdd05564563ae6a6b1632f60284d9a7aec1fb75ecf4edc3eecd246a2949a" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.13.asok status]
  105. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.729165 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="75b3cdd05564563ae6a6b1632f60284d9a7aec1fb75ecf4edc3eecd246a2949a" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.13.asok status]
  106. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.729259 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="75b3cdd05564563ae6a6b1632f60284d9a7aec1fb75ecf4edc3eecd246a2949a" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.13.asok status]
  107. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.729335 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Liveness" pod="rook-ceph/rook-ceph-osd-13-d695ff7c8-b4kch" podUID=2a96248c-be0e-470a-a6c5-42dbe874b330 containerName="osd"
  108. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.729584 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="38429e8c85041beb73ca14b86b400c2ae52d06beb841a55adf7b7dd00f63229c" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.12.asok status]
  109. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.729687 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="38429e8c85041beb73ca14b86b400c2ae52d06beb841a55adf7b7dd00f63229c" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.12.asok status]
  110. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.729770 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="38429e8c85041beb73ca14b86b400c2ae52d06beb841a55adf7b7dd00f63229c" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.12.asok status]
  111. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.729815 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Liveness" pod="rook-ceph/rook-ceph-osd-12-68c85b8cf4-jp2jc" podUID=df9aed00-5523-4881-b9a1-63c7c13c30a1 containerName="osd"
  112. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.731270 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="21560b83bf578e1440b091863c142639223069077686b2a03f2ce72a2819e66c" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-mon.a.asok mon_status]
  113. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.731359 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="21560b83bf578e1440b091863c142639223069077686b2a03f2ce72a2819e66c" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-mon.a.asok mon_status]
  114. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.731428 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="21560b83bf578e1440b091863c142639223069077686b2a03f2ce72a2819e66c" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-mon.a.asok mon_status]
  115. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.731473 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Liveness" pod="rook-ceph/rook-ceph-mon-a-6645cfb4d-6qffm" podUID=7ac5117c-9f5a-40b6-92fa-cdd1b34fcb3a containerName="mon"
  116. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.732393 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="3b87fd8bfd3fc29f0f30be157f5ec23859b4f4ad3a97ec1c4b4e305c8f984fcb" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.8.asok status]
  117. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.732514 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="3b87fd8bfd3fc29f0f30be157f5ec23859b4f4ad3a97ec1c4b4e305c8f984fcb" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.8.asok status]
  118. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.732597 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="3b87fd8bfd3fc29f0f30be157f5ec23859b4f4ad3a97ec1c4b4e305c8f984fcb" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.8.asok status]
  119. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.732641 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Liveness" pod="rook-ceph/rook-ceph-osd-8-67df699b4f-xzr6w" podUID=6d35c240-6a70-48d0-b19a-931e728b7438 containerName="osd"
  120. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.732819 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="d6610fe14fdcb47110db360c013563b52f8169075b632791391ce6984c0fe336" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.15.asok status]
  121. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.732909 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="d6610fe14fdcb47110db360c013563b52f8169075b632791391ce6984c0fe336" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.15.asok status]
  122. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.732983 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="d6610fe14fdcb47110db360c013563b52f8169075b632791391ce6984c0fe336" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.15.asok status]
  123. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.733026 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Liveness" pod="rook-ceph/rook-ceph-osd-15-8456b6f56c-sclr9" podUID=b6b4a560-b5a7-4bce-a7fc-cc45a9657da9 containerName="osd"
  124. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.733262 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="639ca1de18575830360cc1efa4611bc04d717b434b795dbce980b9c86c09ac1a" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.10.asok status]
  125. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.733359 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="639ca1de18575830360cc1efa4611bc04d717b434b795dbce980b9c86c09ac1a" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.10.asok status]
  126. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.733444 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="639ca1de18575830360cc1efa4611bc04d717b434b795dbce980b9c86c09ac1a" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.10.asok status]
  127. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.733489 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Liveness" pod="rook-ceph/rook-ceph-osd-10-77d5fd96b4-blrfj" podUID=77f2b7b1-f6e7-49d4-b26e-cd6941ffd117 containerName="osd"
  128. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.734708 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="22a0f080979e3156b222d13f52875489810e960c7956622ae6f56609e672c7ea" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.3.asok status]
  129. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.734807 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="22a0f080979e3156b222d13f52875489810e960c7956622ae6f56609e672c7ea" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.3.asok status]
  130. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.734905 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="22a0f080979e3156b222d13f52875489810e960c7956622ae6f56609e672c7ea" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-osd.3.asok status]
  131. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.734965 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Liveness" pod="rook-ceph/rook-ceph-osd-3-7c9974db95-5zttn" podUID=6c9cf75d-5e76-4827-a028-984cec3cde0c containerName="osd"
  132. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.801400 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="945270d33bdd09614f45610743198118530f7ff64b273424212ce22fdccc89aa" cmd=[/bin/calico-node -bird-ready -felix-ready]
  133. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.801400 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="945270d33bdd09614f45610743198118530f7ff64b273424212ce22fdccc89aa" cmd=[/bin/calico-node -felix-live -bird-live]
  134. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.801580 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="945270d33bdd09614f45610743198118530f7ff64b273424212ce22fdccc89aa" cmd=[/bin/calico-node -bird-ready -felix-ready]
  135. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.801698 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="945270d33bdd09614f45610743198118530f7ff64b273424212ce22fdccc89aa" cmd=[/bin/calico-node -bird-ready -felix-ready]
  136. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.801776 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Readiness" pod="kube-system/calico-node-g5lkc" podUID=c09b82a6-17a1-4d75-80d1-e3340dccd3ed containerName="calico-node"
  137. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.801698 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="945270d33bdd09614f45610743198118530f7ff64b273424212ce22fdccc89aa" cmd=[/bin/calico-node -felix-live -bird-live]
  138. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.801937 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="945270d33bdd09614f45610743198118530f7ff64b273424212ce22fdccc89aa" cmd=[/bin/calico-node -felix-live -bird-live]
  139. Dec 02 03:15:37 k8s-node0 kubelet[4427]: E1202 03:15:37.801989 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Liveness" pod="kube-system/calico-node-g5lkc" podUID=c09b82a6-17a1-4d75-80d1-e3340dccd3ed containerName="calico-node"
  140. Dec 02 03:15:38 k8s-node0 kubelet[4427]: E1202 03:15:38.144904 4427 remote_runtime.go:207] "ListPodSandbox with filter from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" filter="nil"
  141. Dec 02 03:15:38 k8s-node0 kubelet[4427]: E1202 03:15:38.144956 4427 kuberuntime_sandbox.go:223] "Failed to list pod sandboxes" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  142. Dec 02 03:15:38 k8s-node0 kubelet[4427]: E1202 03:15:38.144993 4427 generic.go:205] "GenericPLEG: Unable to retrieve pods" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  143. Dec 02 03:15:39 k8s-node0 kubelet[4427]: E1202 03:15:39.146118 4427 remote_runtime.go:207] "ListPodSandbox with filter from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" filter="nil"
  144. Dec 02 03:15:39 k8s-node0 kubelet[4427]: E1202 03:15:39.146174 4427 kuberuntime_sandbox.go:223] "Failed to list pod sandboxes" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  145. Dec 02 03:15:39 k8s-node0 kubelet[4427]: E1202 03:15:39.146213 4427 generic.go:205] "GenericPLEG: Unable to retrieve pods" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  146. Dec 02 03:15:39 k8s-node0 kubelet[4427]: E1202 03:15:39.255852 4427 remote_runtime.go:207] "ListPodSandbox with filter from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" filter="&PodSandboxFilter{Id:,State:&PodSandboxStateValue{State:SANDBOX_READY,},LabelSelector:map[string]string{},}"
  147. Dec 02 03:15:39 k8s-node0 kubelet[4427]: E1202 03:15:39.255905 4427 kuberuntime_sandbox.go:223] "Failed to list pod sandboxes" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  148. Dec 02 03:15:39 k8s-node0 kubelet[4427]: E1202 03:15:39.255945 4427 kubelet_pods.go:1107] "Error listing containers" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  149. Dec 02 03:15:39 k8s-node0 kubelet[4427]: E1202 03:15:39.255968 4427 kubelet.go:2011] "Failed cleaning pods" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  150. Dec 02 03:15:39 k8s-node0 kubelet[4427]: E1202 03:15:39.712565 4427 remote_image.go:152] "ImageFsInfo from image service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  151. Dec 02 03:15:39 k8s-node0 kubelet[4427]: E1202 03:15:39.712608 4427 eviction_manager.go:255] "Eviction manager: failed to get summary stats" err="failed to get imageFs stats: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  152. Dec 02 03:15:39 k8s-node0 kubelet[4427]: E1202 03:15:39.948174 4427 remote_runtime.go:515] "Status from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  153. Dec 02 03:15:39 k8s-node0 kubelet[4427]: E1202 03:15:39.948234 4427 kubelet.go:2200] "Container runtime sanity check failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  154. Dec 02 03:15:40 k8s-node0 kubelet[4427]: E1202 03:15:40.089599 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="832e93e34cb92a96ce4d94ba9781c8c7a6841c88cdd74209b2b4030798b6c1f8" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-mds.ceph-filesystem-b.asok status]
  155. Dec 02 03:15:40 k8s-node0 kubelet[4427]: E1202 03:15:40.089691 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="832e93e34cb92a96ce4d94ba9781c8c7a6841c88cdd74209b2b4030798b6c1f8" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-mds.ceph-filesystem-b.asok status]
  156. Dec 02 03:15:40 k8s-node0 kubelet[4427]: E1202 03:15:40.089756 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="832e93e34cb92a96ce4d94ba9781c8c7a6841c88cdd74209b2b4030798b6c1f8" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-mds.ceph-filesystem-b.asok status]
  157. Dec 02 03:15:40 k8s-node0 kubelet[4427]: E1202 03:15:40.089807 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Liveness" pod="rook-ceph/rook-ceph-mds-ceph-filesystem-b-5dd6d8cfbc-nxmxr" podUID=8aa7e1a5-75d5-4b8c-aa6b-067bac0efe0c containerName="mds"
  158. Dec 02 03:15:40 k8s-node0 kubelet[4427]: E1202 03:15:40.096836 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="d615c143a9b42a21e462606a6844daac5f1100e8340a54555bade79714b7e896" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-mgr.a.asok status]
  159. Dec 02 03:15:40 k8s-node0 kubelet[4427]: E1202 03:15:40.096933 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="d615c143a9b42a21e462606a6844daac5f1100e8340a54555bade79714b7e896" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-mgr.a.asok status]
  160. Dec 02 03:15:40 k8s-node0 kubelet[4427]: E1202 03:15:40.097003 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="d615c143a9b42a21e462606a6844daac5f1100e8340a54555bade79714b7e896" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-mgr.a.asok status]
  161. Dec 02 03:15:40 k8s-node0 kubelet[4427]: E1202 03:15:40.097048 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Liveness" pod="rook-ceph/rook-ceph-mgr-a-8cd967954-thshl" podUID=2f8c8c49-f630-4973-aa88-9243d72163ed containerName="mgr"
  162. Dec 02 03:15:40 k8s-node0 kubelet[4427]: E1202 03:15:40.100732 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="3582dda4b15a21513ef806e2a25edd7056edbbe5b5ab3aa6c8e9fdbf5472e2a8" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-mds.ceph-filesystem-a.asok status]
  163. Dec 02 03:15:40 k8s-node0 kubelet[4427]: E1202 03:15:40.100832 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="3582dda4b15a21513ef806e2a25edd7056edbbe5b5ab3aa6c8e9fdbf5472e2a8" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-mds.ceph-filesystem-a.asok status]
  164. Dec 02 03:15:40 k8s-node0 kubelet[4427]: E1202 03:15:40.100894 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="3582dda4b15a21513ef806e2a25edd7056edbbe5b5ab3aa6c8e9fdbf5472e2a8" cmd=[env -i sh -c ceph --admin-daemon /run/ceph/ceph-mds.ceph-filesystem-a.asok status]
  165. Dec 02 03:15:40 k8s-node0 kubelet[4427]: E1202 03:15:40.100942 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Liveness" pod="rook-ceph/rook-ceph-mds-ceph-filesystem-a-6458859697-nvklh" podUID=062c5ee6-d4a5-4edc-a38a-0876d4139fc9 containerName="mds"
  166. Dec 02 03:15:40 k8s-node0 kubelet[4427]: E1202 03:15:40.146585 4427 remote_runtime.go:207] "ListPodSandbox with filter from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" filter="nil"
  167. Dec 02 03:15:40 k8s-node0 kubelet[4427]: E1202 03:15:40.146635 4427 kuberuntime_sandbox.go:223] "Failed to list pod sandboxes" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  168. Dec 02 03:15:40 k8s-node0 kubelet[4427]: E1202 03:15:40.146674 4427 generic.go:205] "GenericPLEG: Unable to retrieve pods" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  169. Dec 02 03:15:40 k8s-node0 kubelet[4427]: I1202 03:15:40.636980 4427 balancer_conn_wrappers.go:78] pickfirstBalancer: HandleSubConnStateChange: 0xc000b96470, {CONNECTING <nil>}
  170. Dec 02 03:15:41 k8s-node0 kubelet[4427]: E1202 03:15:41.124324 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="92f31f0d5a0094556e8237d5c3903de3fac189a0dd7c6a8a12fc560399ba053e" cmd=[/bin/bash -ec rabbitmq-diagnostics -q ping]
  171. Dec 02 03:15:41 k8s-node0 kubelet[4427]: E1202 03:15:41.124353 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="92f31f0d5a0094556e8237d5c3903de3fac189a0dd7c6a8a12fc560399ba053e" cmd=[/bin/bash -ec rabbitmq-diagnostics -q check_running && rabbitmq-diagnostics -q check_local_alarms]
  172. Dec 02 03:15:41 k8s-node0 kubelet[4427]: E1202 03:15:41.124438 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="92f31f0d5a0094556e8237d5c3903de3fac189a0dd7c6a8a12fc560399ba053e" cmd=[/bin/bash -ec rabbitmq-diagnostics -q ping]
  173. Dec 02 03:15:41 k8s-node0 kubelet[4427]: E1202 03:15:41.124468 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="92f31f0d5a0094556e8237d5c3903de3fac189a0dd7c6a8a12fc560399ba053e" cmd=[/bin/bash -ec rabbitmq-diagnostics -q check_running && rabbitmq-diagnostics -q check_local_alarms]
  174. Dec 02 03:15:41 k8s-node0 kubelet[4427]: E1202 03:15:41.124512 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="92f31f0d5a0094556e8237d5c3903de3fac189a0dd7c6a8a12fc560399ba053e" cmd=[/bin/bash -ec rabbitmq-diagnostics -q ping]
  175. Dec 02 03:15:41 k8s-node0 kubelet[4427]: E1202 03:15:41.124545 4427 remote_runtime.go:394] "ExecSync cmd from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" containerID="92f31f0d5a0094556e8237d5c3903de3fac189a0dd7c6a8a12fc560399ba053e" cmd=[/bin/bash -ec rabbitmq-diagnostics -q check_running && rabbitmq-diagnostics -q check_local_alarms]
  176. Dec 02 03:15:41 k8s-node0 kubelet[4427]: E1202 03:15:41.124563 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Liveness" pod="rabbitmq-services/rabbitmq-shared-0" podUID=54ece25f-ad85-4a9d-9654-ff512c8839dd containerName="rabbitmq"
  177. Dec 02 03:15:41 k8s-node0 kubelet[4427]: E1202 03:15:41.124600 4427 prober.go:113] "Probe errored" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" probeType="Readiness" pod="rabbitmq-services/rabbitmq-shared-0" podUID=54ece25f-ad85-4a9d-9654-ff512c8839dd containerName="rabbitmq"
  178. Dec 02 03:15:41 k8s-node0 kubelet[4427]: E1202 03:15:41.147725 4427 remote_runtime.go:207] "ListPodSandbox with filter from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" filter="nil"
  179. Dec 02 03:15:41 k8s-node0 kubelet[4427]: E1202 03:15:41.147783 4427 kuberuntime_sandbox.go:223] "Failed to list pod sandboxes" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  180. Dec 02 03:15:41 k8s-node0 kubelet[4427]: E1202 03:15:41.147826 4427 generic.go:205] "GenericPLEG: Unable to retrieve pods" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  181. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Scheduled restart job, restart counter is at 3.
  182. -- Subject: Automatic restarting of a unit has been scheduled
  183. -- Defined-By: systemd
  184. -- Support: http://www.ubuntu.com/support
  185. --
  186. -- Automatic restarting of the unit containerd.service has been scheduled, as the result for
  187. -- the configured Restart= setting for the unit.
  188. Dec 02 03:15:41 k8s-node0 systemd[1]: Stopped containerd container runtime.
  189. -- Subject: A stop job for unit containerd.service has finished
  190. -- Defined-By: systemd
  191. -- Support: http://www.ubuntu.com/support
  192. --
  193. -- A stop job for unit containerd.service has finished.
  194. --
  195. -- The job identifier is 11855 and the job result is done.
  196. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4656 (containerd-shim) in control group while starting unit. Ignoring.
  197. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  198. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4660 (containerd-shim) in control group while starting unit. Ignoring.
  199. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  200. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4664 (containerd-shim) in control group while starting unit. Ignoring.
  201. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  202. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4768 (containerd-shim) in control group while starting unit. Ignoring.
  203. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  204. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4777 (containerd-shim) in control group while starting unit. Ignoring.
  205. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  206. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4784 (containerd-shim) in control group while starting unit. Ignoring.
  207. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  208. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4878 (containerd-shim) in control group while starting unit. Ignoring.
  209. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  210. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4917 (containerd-shim) in control group while starting unit. Ignoring.
  211. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  212. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6070 (containerd-shim) in control group while starting unit. Ignoring.
  213. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  214. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6112 (containerd-shim) in control group while starting unit. Ignoring.
  215. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  216. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6137 (containerd-shim) in control group while starting unit. Ignoring.
  217. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  218. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6176 (containerd-shim) in control group while starting unit. Ignoring.
  219. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  220. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6185 (containerd-shim) in control group while starting unit. Ignoring.
  221. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  222. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6240 (containerd-shim) in control group while starting unit. Ignoring.
  223. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  224. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6272 (containerd-shim) in control group while starting unit. Ignoring.
  225. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  226. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6342 (containerd-shim) in control group while starting unit. Ignoring.
  227. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  228. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6367 (containerd-shim) in control group while starting unit. Ignoring.
  229. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  230. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6383 (containerd-shim) in control group while starting unit. Ignoring.
  231. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  232. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6392 (containerd-shim) in control group while starting unit. Ignoring.
  233. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  234. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6434 (containerd-shim) in control group while starting unit. Ignoring.
  235. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  236. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6498 (containerd-shim) in control group while starting unit. Ignoring.
  237. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  238. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6540 (containerd-shim) in control group while starting unit. Ignoring.
  239. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  240. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6620 (containerd-shim) in control group while starting unit. Ignoring.
  241. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  242. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6736 (containerd-shim) in control group while starting unit. Ignoring.
  243. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  244. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8169 (containerd-shim) in control group while starting unit. Ignoring.
  245. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  246. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8214 (containerd-shim) in control group while starting unit. Ignoring.
  247. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  248. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8407 (containerd-shim) in control group while starting unit. Ignoring.
  249. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  250. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8457 (containerd-shim) in control group while starting unit. Ignoring.
  251. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  252. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8496 (containerd-shim) in control group while starting unit. Ignoring.
  253. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  254. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8609 (containerd-shim) in control group while starting unit. Ignoring.
  255. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  256. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8668 (containerd-shim) in control group while starting unit. Ignoring.
  257. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  258. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8776 (containerd-shim) in control group while starting unit. Ignoring.
  259. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  260. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8884 (containerd-shim) in control group while starting unit. Ignoring.
  261. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  262. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8963 (containerd-shim) in control group while starting unit. Ignoring.
  263. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  264. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8985 (containerd-shim) in control group while starting unit. Ignoring.
  265. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  266. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9040 (containerd-shim) in control group while starting unit. Ignoring.
  267. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  268. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9664 (containerd-shim) in control group while starting unit. Ignoring.
  269. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  270. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 10262 (containerd-shim) in control group while starting unit. Ignoring.
  271. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  272. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11445 (containerd-shim) in control group while starting unit. Ignoring.
  273. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  274. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11454 (containerd-shim) in control group while starting unit. Ignoring.
  275. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  276. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11477 (containerd-shim) in control group while starting unit. Ignoring.
  277. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  278. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11487 (containerd-shim) in control group while starting unit. Ignoring.
  279. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  280. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11496 (containerd-shim) in control group while starting unit. Ignoring.
  281. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  282. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11511 (containerd-shim) in control group while starting unit. Ignoring.
  283. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  284. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11515 (containerd-shim) in control group while starting unit. Ignoring.
  285. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  286. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 12335 (containerd-shim) in control group while starting unit. Ignoring.
  287. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  288. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 12360 (containerd-shim) in control group while starting unit. Ignoring.
  289. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  290. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 12370 (containerd-shim) in control group while starting unit. Ignoring.
  291. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  292. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 18662 (containerd-shim) in control group while starting unit. Ignoring.
  293. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  294. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 18752 (containerd-shim) in control group while starting unit. Ignoring.
  295. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  296. Dec 02 03:15:41 k8s-node0 kubelet[4427]: E1202 03:15:41.257450 4427 remote_runtime.go:207] "ListPodSandbox with filter from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" filter="&PodSandboxFilter{Id:,State:&PodSandboxStateValue{State:SANDBOX_READY,},LabelSelector:map[string]string{},}"
  297. Dec 02 03:15:41 k8s-node0 kubelet[4427]: E1202 03:15:41.257494 4427 kuberuntime_sandbox.go:223] "Failed to list pod sandboxes" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  298. Dec 02 03:15:41 k8s-node0 kubelet[4427]: E1202 03:15:41.257515 4427 kubelet_pods.go:1107] "Error listing containers" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  299. Dec 02 03:15:41 k8s-node0 kubelet[4427]: E1202 03:15:41.257545 4427 kubelet.go:2011] "Failed cleaning pods" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  300. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 18858 (containerd-shim) in control group while starting unit. Ignoring.
  301. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  302. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 18992 (containerd-shim) in control group while starting unit. Ignoring.
  303. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  304. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 19093 (containerd-shim) in control group while starting unit. Ignoring.
  305. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  306. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 19611 (containerd-shim) in control group while starting unit. Ignoring.
  307. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  308. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 19684 (containerd-shim) in control group while starting unit. Ignoring.
  309. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  310. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 20534 (containerd-shim) in control group while starting unit. Ignoring.
  311. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  312. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 20742 (containerd-shim) in control group while starting unit. Ignoring.
  313. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  314. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21145 (containerd-shim) in control group while starting unit. Ignoring.
  315. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  316. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21174 (containerd-shim) in control group while starting unit. Ignoring.
  317. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  318. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21431 (containerd-shim) in control group while starting unit. Ignoring.
  319. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  320. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21466 (containerd-shim) in control group while starting unit. Ignoring.
  321. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  322. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 22464 (containerd-shim) in control group while starting unit. Ignoring.
  323. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  324. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 22506 (containerd-shim) in control group while starting unit. Ignoring.
  325. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  326. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 22542 (containerd-shim) in control group while starting unit. Ignoring.
  327. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  328. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 22985 (containerd-shim) in control group while starting unit. Ignoring.
  329. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  330. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 23122 (containerd-shim) in control group while starting unit. Ignoring.
  331. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  332. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 23197 (containerd-shim) in control group while starting unit. Ignoring.
  333. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  334. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 24251 (containerd-shim) in control group while starting unit. Ignoring.
  335. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  336. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 24971 (containerd-shim) in control group while starting unit. Ignoring.
  337. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  338. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 25035 (containerd-shim) in control group while starting unit. Ignoring.
  339. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  340. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 451676 (containerd-shim) in control group while starting unit. Ignoring.
  341. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  342. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452053 (containerd-shim) in control group while starting unit. Ignoring.
  343. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  344. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452185 (containerd-shim) in control group while starting unit. Ignoring.
  345. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  346. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452232 (containerd-shim) in control group while starting unit. Ignoring.
  347. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  348. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452251 (containerd-shim) in control group while starting unit. Ignoring.
  349. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  350. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452616 (containerd-shim) in control group while starting unit. Ignoring.
  351. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  352. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452948 (containerd-shim) in control group while starting unit. Ignoring.
  353. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  354. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452954 (containerd-shim) in control group while starting unit. Ignoring.
  355. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  356. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 455324 (containerd-shim) in control group while starting unit. Ignoring.
  357. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  358. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 455769 (containerd-shim) in control group while starting unit. Ignoring.
  359. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  360. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4711 (pause) in control group while starting unit. Ignoring.
  361. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  362. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4710 (pause) in control group while starting unit. Ignoring.
  363. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  364. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4709 (pause) in control group while starting unit. Ignoring.
  365. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  366. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4821 (kube-apiserver) in control group while starting unit. Ignoring.
  367. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  368. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4822 (etcd) in control group while starting unit. Ignoring.
  369. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  370. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4823 (kube-scheduler) in control group while starting unit. Ignoring.
  371. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  372. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4896 (pause) in control group while starting unit. Ignoring.
  373. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  374. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4942 (kube-controller) in control group while starting unit. Ignoring.
  375. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  376. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6088 (pause) in control group while starting unit. Ignoring.
  377. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  378. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6132 (pause) in control group while starting unit. Ignoring.
  379. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  380. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6159 (node_exporter) in control group while starting unit. Ignoring.
  381. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  382. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6210 (pause) in control group while starting unit. Ignoring.
  383. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  384. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6211 (pause) in control group while starting unit. Ignoring.
  385. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  386. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6293 (node-cache) in control group while starting unit. Ignoring.
  387. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  388. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6294 (pause) in control group while starting unit. Ignoring.
  389. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  390. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6362 (kube-proxy) in control group while starting unit. Ignoring.
  391. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  392. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6418 (cephcsi) in control group while starting unit. Ignoring.
  393. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  394. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6419 (speaker) in control group while starting unit. Ignoring.
  395. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  396. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6425 (pause) in control group while starting unit. Ignoring.
  397. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  398. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6470 (pause) in control group while starting unit. Ignoring.
  399. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  400. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6517 (csi-node-driver) in control group while starting unit. Ignoring.
  401. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  402. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6594 (cephcsi) in control group while starting unit. Ignoring.
  403. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  404. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6686 (cephcsi) in control group while starting unit. Ignoring.
  405. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  406. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6786 (cephcsi) in control group while starting unit. Ignoring.
  407. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  408. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8279 (pause) in control group while starting unit. Ignoring.
  409. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  410. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8281 (pause) in control group while starting unit. Ignoring.
  411. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  412. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8428 (pause) in control group while starting unit. Ignoring.
  413. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  414. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8476 (pause) in control group while starting unit. Ignoring.
  415. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  416. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8527 (pause) in control group while starting unit. Ignoring.
  417. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  418. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8651 (pause) in control group while starting unit. Ignoring.
  419. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  420. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8692 (pause) in control group while starting unit. Ignoring.
  421. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  422. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8829 (pause) in control group while starting unit. Ignoring.
  423. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  424. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8923 (pause) in control group while starting unit. Ignoring.
  425. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  426. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9005 (pause) in control group while starting unit. Ignoring.
  427. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  428. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9012 (pause) in control group while starting unit. Ignoring.
  429. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  430. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9135 (runsvdir) in control group while starting unit. Ignoring.
  431. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  432. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9794 (runsv) in control group while starting unit. Ignoring.
  433. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  434. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9795 (runsv) in control group while starting unit. Ignoring.
  435. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  436. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9796 (runsv) in control group while starting unit. Ignoring.
  437. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  438. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9797 (runsv) in control group while starting unit. Ignoring.
  439. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  440. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9798 (runsv) in control group while starting unit. Ignoring.
  441. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  442. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9799 (runsv) in control group while starting unit. Ignoring.
  443. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  444. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9800 (runsv) in control group while starting unit. Ignoring.
  445. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  446. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9801 (calico-node) in control group while starting unit. Ignoring.
  447. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  448. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9803 (calico-node) in control group while starting unit. Ignoring.
  449. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  450. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9804 (calico-node) in control group while starting unit. Ignoring.
  451. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  452. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9805 (calico-node) in control group while starting unit. Ignoring.
  453. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  454. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9807 (calico-node) in control group while starting unit. Ignoring.
  455. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  456. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 10190 (bird6) in control group while starting unit. Ignoring.
  457. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  458. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 10191 (bird) in control group while starting unit. Ignoring.
  459. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  460. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9712 (ceph-mon) in control group while starting unit. Ignoring.
  461. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  462. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 10280 (csi-node-driver) in control group while starting unit. Ignoring.
  463. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  464. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11482 (ceph-osd) in control group while starting unit. Ignoring.
  465. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  466. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11510 (ceph-osd) in control group while starting unit. Ignoring.
  467. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  468. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11564 (ceph-osd) in control group while starting unit. Ignoring.
  469. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  470. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11576 (ceph-osd) in control group while starting unit. Ignoring.
  471. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  472. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11579 (ceph-osd) in control group while starting unit. Ignoring.
  473. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  474. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11587 (ceph-osd) in control group while starting unit. Ignoring.
  475. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  476. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11595 (ceph-osd) in control group while starting unit. Ignoring.
  477. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  478. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 12543 (ceph-osd) in control group while starting unit. Ignoring.
  479. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  480. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 12545 (ceph-osd) in control group while starting unit. Ignoring.
  481. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  482. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 12550 (ceph-osd) in control group while starting unit. Ignoring.
  483. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  484. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 18709 (pause) in control group while starting unit. Ignoring.
  485. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  486. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 18796 (pause) in control group while starting unit. Ignoring.
  487. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  488. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 18893 (rabbitmq-server) in control group while starting unit. Ignoring.
  489. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  490. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 19667 (epmd) in control group while starting unit. Ignoring.
  491. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  492. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 20040 (beam.smp) in control group while starting unit. Ignoring.
  493. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  494. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 20047 (erl_child_setup) in control group while starting unit. Ignoring.
  495. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  496. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 20405 (inet_gethost) in control group while starting unit. Ignoring.
  497. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  498. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 20406 (inet_gethost) in control group while starting unit. Ignoring.
  499. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  500. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 19028 (pause) in control group while starting unit. Ignoring.
  501. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  502. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 19154 (postgres) in control group while starting unit. Ignoring.
  503. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  504. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21611 (postgres) in control group while starting unit. Ignoring.
  505. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  506. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21705 (postgres) in control group while starting unit. Ignoring.
  507. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  508. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21706 (postgres) in control group while starting unit. Ignoring.
  509. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  510. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21708 (postgres) in control group while starting unit. Ignoring.
  511. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  512. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21807 (postgres) in control group while starting unit. Ignoring.
  513. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  514. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 19646 (postgres) in control group while starting unit. Ignoring.
  515. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  516. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21808 (postgres) in control group while starting unit. Ignoring.
  517. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  518. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21809 (postgres) in control group while starting unit. Ignoring.
  519. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  520. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21810 (postgres) in control group while starting unit. Ignoring.
  521. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  522. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21811 (postgres) in control group while starting unit. Ignoring.
  523. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  524. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21812 (postgres) in control group while starting unit. Ignoring.
  525. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  526. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21813 (postgres) in control group while starting unit. Ignoring.
  527. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  528. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21906 (postgres) in control group while starting unit. Ignoring.
  529. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  530. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 22665 (postgres) in control group while starting unit. Ignoring.
  531. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  532. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 23856 (postgres) in control group while starting unit. Ignoring.
  533. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  534. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 2146874 (postgres) in control group while starting unit. Ignoring.
  535. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  536. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 19824 (postgres_export) in control group while starting unit. Ignoring.
  537. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  538. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 20556 (pause) in control group while starting unit. Ignoring.
  539. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  540. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 20871 (pause) in control group while starting unit. Ignoring.
  541. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  542. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21162 (redis-server) in control group while starting unit. Ignoring.
  543. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  544. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21191 (pilot-agent) in control group while starting unit. Ignoring.
  545. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  546. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21290 (envoy) in control group while starting unit. Ignoring.
  547. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  548. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21448 (scanner-trivy) in control group while starting unit. Ignoring.
  549. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  550. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21495 (pilot-agent) in control group while starting unit. Ignoring.
  551. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  552. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21542 (envoy) in control group while starting unit. Ignoring.
  553. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  554. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 22485 (pause) in control group while starting unit. Ignoring.
  555. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  556. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 22525 (alertmanager) in control group while starting unit. Ignoring.
  557. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  558. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 22561 (prometheus-conf) in control group while starting unit. Ignoring.
  559. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  560. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 23007 (pause) in control group while starting unit. Ignoring.
  561. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  562. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 23159 (prometheus) in control group while starting unit. Ignoring.
  563. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  564. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 23218 (prometheus-conf) in control group while starting unit. Ignoring.
  565. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  566. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 24273 (pause) in control group while starting unit. Ignoring.
  567. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  568. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 24991 (s6-svscan) in control group while starting unit. Ignoring.
  569. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  570. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 25067 (s6-supervise) in control group while starting unit. Ignoring.
  571. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  572. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 25685 (s6-supervise) in control group while starting unit. Ignoring.
  573. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  574. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 25688 (Plex Media Serv) in control group while starting unit. Ignoring.
  575. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  576. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 26077 (Plex Script Hos) in control group while starting unit. Ignoring.
  577. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  578. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 26505 (Plex Tuner Serv) in control group while starting unit. Ignoring.
  579. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  580. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 173484 (EasyAudioEncode) in control group while starting unit. Ignoring.
  581. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  582. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 25094 (pilot-agent) in control group while starting unit. Ignoring.
  583. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  584. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 25412 (envoy) in control group while starting unit. Ignoring.
  585. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  586. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 451726 (pause) in control group while starting unit. Ignoring.
  587. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  588. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452109 (pause) in control group while starting unit. Ignoring.
  589. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  590. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452295 (pause) in control group while starting unit. Ignoring.
  591. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  592. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452280 (pause) in control group while starting unit. Ignoring.
  593. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  594. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452272 (tini) in control group while starting unit. Ignoring.
  595. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  596. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452375 (toolbox.sh) in control group while starting unit. Ignoring.
  597. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  598. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 2179753 (sleep) in control group while starting unit. Ignoring.
  599. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  600. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452642 (ceph-mds) in control group while starting unit. Ignoring.
  601. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  602. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 453022 (ceph-mds) in control group while starting unit. Ignoring.
  603. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  604. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 453017 (ceph-mgr) in control group while starting unit. Ignoring.
  605. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  606. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 455348 (pause) in control group while starting unit. Ignoring.
  607. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  608. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 455791 (ceph-crash) in control group while starting unit. Ignoring.
  609. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  610. Dec 02 03:15:41 k8s-node0 systemd[1]: Starting containerd container runtime...
  611. -- Subject: A start job for unit containerd.service has begun execution
  612. -- Defined-By: systemd
  613. -- Support: http://www.ubuntu.com/support
  614. --
  615. -- A start job for unit containerd.service has begun execution.
  616. --
  617. -- The job identifier is 11855.
  618. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4656 (containerd-shim) in control group while starting unit. Ignoring.
  619. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  620. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4660 (containerd-shim) in control group while starting unit. Ignoring.
  621. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  622. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4664 (containerd-shim) in control group while starting unit. Ignoring.
  623. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  624. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4768 (containerd-shim) in control group while starting unit. Ignoring.
  625. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  626. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4777 (containerd-shim) in control group while starting unit. Ignoring.
  627. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  628. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4784 (containerd-shim) in control group while starting unit. Ignoring.
  629. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  630. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4878 (containerd-shim) in control group while starting unit. Ignoring.
  631. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  632. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4917 (containerd-shim) in control group while starting unit. Ignoring.
  633. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  634. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6070 (containerd-shim) in control group while starting unit. Ignoring.
  635. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  636. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6112 (containerd-shim) in control group while starting unit. Ignoring.
  637. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  638. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6137 (containerd-shim) in control group while starting unit. Ignoring.
  639. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  640. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6176 (containerd-shim) in control group while starting unit. Ignoring.
  641. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  642. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6185 (containerd-shim) in control group while starting unit. Ignoring.
  643. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  644. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6240 (containerd-shim) in control group while starting unit. Ignoring.
  645. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  646. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6272 (containerd-shim) in control group while starting unit. Ignoring.
  647. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  648. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6342 (containerd-shim) in control group while starting unit. Ignoring.
  649. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  650. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6367 (containerd-shim) in control group while starting unit. Ignoring.
  651. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  652. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6383 (containerd-shim) in control group while starting unit. Ignoring.
  653. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  654. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6392 (containerd-shim) in control group while starting unit. Ignoring.
  655. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  656. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6434 (containerd-shim) in control group while starting unit. Ignoring.
  657. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  658. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6498 (containerd-shim) in control group while starting unit. Ignoring.
  659. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  660. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6540 (containerd-shim) in control group while starting unit. Ignoring.
  661. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  662. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6620 (containerd-shim) in control group while starting unit. Ignoring.
  663. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  664. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6736 (containerd-shim) in control group while starting unit. Ignoring.
  665. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  666. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8169 (containerd-shim) in control group while starting unit. Ignoring.
  667. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  668. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8214 (containerd-shim) in control group while starting unit. Ignoring.
  669. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  670. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8407 (containerd-shim) in control group while starting unit. Ignoring.
  671. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  672. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8457 (containerd-shim) in control group while starting unit. Ignoring.
  673. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  674. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8496 (containerd-shim) in control group while starting unit. Ignoring.
  675. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  676. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8609 (containerd-shim) in control group while starting unit. Ignoring.
  677. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  678. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8668 (containerd-shim) in control group while starting unit. Ignoring.
  679. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  680. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8776 (containerd-shim) in control group while starting unit. Ignoring.
  681. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  682. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8884 (containerd-shim) in control group while starting unit. Ignoring.
  683. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  684. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8963 (containerd-shim) in control group while starting unit. Ignoring.
  685. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  686. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8985 (containerd-shim) in control group while starting unit. Ignoring.
  687. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  688. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9040 (containerd-shim) in control group while starting unit. Ignoring.
  689. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  690. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9664 (containerd-shim) in control group while starting unit. Ignoring.
  691. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  692. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 10262 (containerd-shim) in control group while starting unit. Ignoring.
  693. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  694. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11445 (containerd-shim) in control group while starting unit. Ignoring.
  695. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  696. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11454 (containerd-shim) in control group while starting unit. Ignoring.
  697. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  698. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11477 (containerd-shim) in control group while starting unit. Ignoring.
  699. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  700. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11487 (containerd-shim) in control group while starting unit. Ignoring.
  701. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  702. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11496 (containerd-shim) in control group while starting unit. Ignoring.
  703. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  704. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11511 (containerd-shim) in control group while starting unit. Ignoring.
  705. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  706. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11515 (containerd-shim) in control group while starting unit. Ignoring.
  707. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  708. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 12335 (containerd-shim) in control group while starting unit. Ignoring.
  709. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  710. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 12360 (containerd-shim) in control group while starting unit. Ignoring.
  711. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  712. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 12370 (containerd-shim) in control group while starting unit. Ignoring.
  713. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  714. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 18662 (containerd-shim) in control group while starting unit. Ignoring.
  715. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  716. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 18752 (containerd-shim) in control group while starting unit. Ignoring.
  717. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  718. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 18858 (containerd-shim) in control group while starting unit. Ignoring.
  719. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  720. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 18992 (containerd-shim) in control group while starting unit. Ignoring.
  721. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  722. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 19093 (containerd-shim) in control group while starting unit. Ignoring.
  723. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  724. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 19611 (containerd-shim) in control group while starting unit. Ignoring.
  725. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  726. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 19684 (containerd-shim) in control group while starting unit. Ignoring.
  727. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  728. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 20534 (containerd-shim) in control group while starting unit. Ignoring.
  729. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  730. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 20742 (containerd-shim) in control group while starting unit. Ignoring.
  731. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  732. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21145 (containerd-shim) in control group while starting unit. Ignoring.
  733. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  734. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21174 (containerd-shim) in control group while starting unit. Ignoring.
  735. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  736. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21431 (containerd-shim) in control group while starting unit. Ignoring.
  737. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  738. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21466 (containerd-shim) in control group while starting unit. Ignoring.
  739. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  740. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 22464 (containerd-shim) in control group while starting unit. Ignoring.
  741. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  742. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 22506 (containerd-shim) in control group while starting unit. Ignoring.
  743. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  744. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 22542 (containerd-shim) in control group while starting unit. Ignoring.
  745. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  746. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 22985 (containerd-shim) in control group while starting unit. Ignoring.
  747. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  748. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 23122 (containerd-shim) in control group while starting unit. Ignoring.
  749. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  750. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 23197 (containerd-shim) in control group while starting unit. Ignoring.
  751. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  752. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 24251 (containerd-shim) in control group while starting unit. Ignoring.
  753. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  754. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 24971 (containerd-shim) in control group while starting unit. Ignoring.
  755. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  756. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 25035 (containerd-shim) in control group while starting unit. Ignoring.
  757. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  758. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 451676 (containerd-shim) in control group while starting unit. Ignoring.
  759. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  760. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452053 (containerd-shim) in control group while starting unit. Ignoring.
  761. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  762. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452185 (containerd-shim) in control group while starting unit. Ignoring.
  763. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  764. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452232 (containerd-shim) in control group while starting unit. Ignoring.
  765. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  766. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452251 (containerd-shim) in control group while starting unit. Ignoring.
  767. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  768. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452616 (containerd-shim) in control group while starting unit. Ignoring.
  769. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  770. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452948 (containerd-shim) in control group while starting unit. Ignoring.
  771. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  772. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452954 (containerd-shim) in control group while starting unit. Ignoring.
  773. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  774. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 455324 (containerd-shim) in control group while starting unit. Ignoring.
  775. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  776. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 455769 (containerd-shim) in control group while starting unit. Ignoring.
  777. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  778. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4711 (pause) in control group while starting unit. Ignoring.
  779. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  780. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4710 (pause) in control group while starting unit. Ignoring.
  781. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  782. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4709 (pause) in control group while starting unit. Ignoring.
  783. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  784. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4821 (kube-apiserver) in control group while starting unit. Ignoring.
  785. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  786. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4822 (etcd) in control group while starting unit. Ignoring.
  787. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  788. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4823 (kube-scheduler) in control group while starting unit. Ignoring.
  789. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  790. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4896 (pause) in control group while starting unit. Ignoring.
  791. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  792. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 4942 (kube-controller) in control group while starting unit. Ignoring.
  793. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  794. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6088 (pause) in control group while starting unit. Ignoring.
  795. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  796. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6132 (pause) in control group while starting unit. Ignoring.
  797. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  798. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6159 (node_exporter) in control group while starting unit. Ignoring.
  799. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  800. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6210 (pause) in control group while starting unit. Ignoring.
  801. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  802. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6211 (pause) in control group while starting unit. Ignoring.
  803. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  804. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6293 (node-cache) in control group while starting unit. Ignoring.
  805. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  806. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6294 (pause) in control group while starting unit. Ignoring.
  807. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  808. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6362 (kube-proxy) in control group while starting unit. Ignoring.
  809. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  810. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6418 (cephcsi) in control group while starting unit. Ignoring.
  811. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  812. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6419 (speaker) in control group while starting unit. Ignoring.
  813. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  814. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6425 (pause) in control group while starting unit. Ignoring.
  815. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  816. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6470 (pause) in control group while starting unit. Ignoring.
  817. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  818. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6517 (csi-node-driver) in control group while starting unit. Ignoring.
  819. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  820. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6594 (cephcsi) in control group while starting unit. Ignoring.
  821. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  822. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6686 (cephcsi) in control group while starting unit. Ignoring.
  823. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  824. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 6786 (cephcsi) in control group while starting unit. Ignoring.
  825. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  826. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8279 (pause) in control group while starting unit. Ignoring.
  827. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  828. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8281 (pause) in control group while starting unit. Ignoring.
  829. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  830. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8428 (pause) in control group while starting unit. Ignoring.
  831. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  832. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8476 (pause) in control group while starting unit. Ignoring.
  833. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  834. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8527 (pause) in control group while starting unit. Ignoring.
  835. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  836. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8651 (pause) in control group while starting unit. Ignoring.
  837. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  838. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8692 (pause) in control group while starting unit. Ignoring.
  839. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  840. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8829 (pause) in control group while starting unit. Ignoring.
  841. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  842. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 8923 (pause) in control group while starting unit. Ignoring.
  843. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  844. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9005 (pause) in control group while starting unit. Ignoring.
  845. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  846. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9012 (pause) in control group while starting unit. Ignoring.
  847. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  848. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9135 (runsvdir) in control group while starting unit. Ignoring.
  849. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  850. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9794 (runsv) in control group while starting unit. Ignoring.
  851. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  852. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9795 (runsv) in control group while starting unit. Ignoring.
  853. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  854. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9796 (runsv) in control group while starting unit. Ignoring.
  855. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  856. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9797 (runsv) in control group while starting unit. Ignoring.
  857. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  858. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9798 (runsv) in control group while starting unit. Ignoring.
  859. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  860. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9799 (runsv) in control group while starting unit. Ignoring.
  861. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  862. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9800 (runsv) in control group while starting unit. Ignoring.
  863. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  864. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9801 (calico-node) in control group while starting unit. Ignoring.
  865. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  866. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9803 (calico-node) in control group while starting unit. Ignoring.
  867. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  868. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9804 (calico-node) in control group while starting unit. Ignoring.
  869. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  870. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9805 (calico-node) in control group while starting unit. Ignoring.
  871. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  872. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9807 (calico-node) in control group while starting unit. Ignoring.
  873. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  874. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 10190 (bird6) in control group while starting unit. Ignoring.
  875. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  876. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 10191 (bird) in control group while starting unit. Ignoring.
  877. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  878. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 9712 (ceph-mon) in control group while starting unit. Ignoring.
  879. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  880. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 10280 (csi-node-driver) in control group while starting unit. Ignoring.
  881. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  882. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11482 (ceph-osd) in control group while starting unit. Ignoring.
  883. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  884. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11510 (ceph-osd) in control group while starting unit. Ignoring.
  885. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  886. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11564 (ceph-osd) in control group while starting unit. Ignoring.
  887. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  888. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11576 (ceph-osd) in control group while starting unit. Ignoring.
  889. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  890. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11579 (ceph-osd) in control group while starting unit. Ignoring.
  891. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  892. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11587 (ceph-osd) in control group while starting unit. Ignoring.
  893. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  894. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 11595 (ceph-osd) in control group while starting unit. Ignoring.
  895. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  896. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 12543 (ceph-osd) in control group while starting unit. Ignoring.
  897. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  898. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 12545 (ceph-osd) in control group while starting unit. Ignoring.
  899. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  900. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 12550 (ceph-osd) in control group while starting unit. Ignoring.
  901. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  902. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 18709 (pause) in control group while starting unit. Ignoring.
  903. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  904. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 18796 (pause) in control group while starting unit. Ignoring.
  905. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  906. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 18893 (rabbitmq-server) in control group while starting unit. Ignoring.
  907. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  908. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 19667 (epmd) in control group while starting unit. Ignoring.
  909. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  910. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 20040 (beam.smp) in control group while starting unit. Ignoring.
  911. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  912. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 20047 (erl_child_setup) in control group while starting unit. Ignoring.
  913. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  914. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 20405 (inet_gethost) in control group while starting unit. Ignoring.
  915. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  916. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 20406 (inet_gethost) in control group while starting unit. Ignoring.
  917. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  918. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 19028 (pause) in control group while starting unit. Ignoring.
  919. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  920. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 19154 (postgres) in control group while starting unit. Ignoring.
  921. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  922. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21611 (postgres) in control group while starting unit. Ignoring.
  923. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  924. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21705 (postgres) in control group while starting unit. Ignoring.
  925. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  926. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21706 (postgres) in control group while starting unit. Ignoring.
  927. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  928. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21708 (postgres) in control group while starting unit. Ignoring.
  929. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  930. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21807 (postgres) in control group while starting unit. Ignoring.
  931. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  932. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 19646 (postgres) in control group while starting unit. Ignoring.
  933. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  934. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21808 (postgres) in control group while starting unit. Ignoring.
  935. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  936. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21809 (postgres) in control group while starting unit. Ignoring.
  937. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  938. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21810 (postgres) in control group while starting unit. Ignoring.
  939. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  940. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21811 (postgres) in control group while starting unit. Ignoring.
  941. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  942. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21812 (postgres) in control group while starting unit. Ignoring.
  943. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  944. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21813 (postgres) in control group while starting unit. Ignoring.
  945. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  946. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21906 (postgres) in control group while starting unit. Ignoring.
  947. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  948. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 22665 (postgres) in control group while starting unit. Ignoring.
  949. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  950. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 23856 (postgres) in control group while starting unit. Ignoring.
  951. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  952. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 2146874 (postgres) in control group while starting unit. Ignoring.
  953. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  954. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 19824 (postgres_export) in control group while starting unit. Ignoring.
  955. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  956. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 20556 (pause) in control group while starting unit. Ignoring.
  957. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  958. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 20871 (pause) in control group while starting unit. Ignoring.
  959. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  960. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21162 (redis-server) in control group while starting unit. Ignoring.
  961. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  962. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21191 (pilot-agent) in control group while starting unit. Ignoring.
  963. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  964. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21290 (envoy) in control group while starting unit. Ignoring.
  965. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  966. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21448 (scanner-trivy) in control group while starting unit. Ignoring.
  967. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  968. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21495 (pilot-agent) in control group while starting unit. Ignoring.
  969. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  970. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 21542 (envoy) in control group while starting unit. Ignoring.
  971. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  972. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 22485 (pause) in control group while starting unit. Ignoring.
  973. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  974. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 22525 (alertmanager) in control group while starting unit. Ignoring.
  975. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  976. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 22561 (prometheus-conf) in control group while starting unit. Ignoring.
  977. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  978. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 23007 (pause) in control group while starting unit. Ignoring.
  979. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  980. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 23159 (prometheus) in control group while starting unit. Ignoring.
  981. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  982. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 23218 (prometheus-conf) in control group while starting unit. Ignoring.
  983. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  984. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 24273 (pause) in control group while starting unit. Ignoring.
  985. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  986. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 24991 (s6-svscan) in control group while starting unit. Ignoring.
  987. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  988. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 25067 (s6-supervise) in control group while starting unit. Ignoring.
  989. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  990. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 25685 (s6-supervise) in control group while starting unit. Ignoring.
  991. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  992. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 25688 (Plex Media Serv) in control group while starting unit. Ignoring.
  993. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  994. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 26077 (Plex Script Hos) in control group while starting unit. Ignoring.
  995. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  996. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 26505 (Plex Tuner Serv) in control group while starting unit. Ignoring.
  997. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  998. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 173484 (EasyAudioEncode) in control group while starting unit. Ignoring.
  999. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  1000. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 25094 (pilot-agent) in control group while starting unit. Ignoring.
  1001. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  1002. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 25412 (envoy) in control group while starting unit. Ignoring.
  1003. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  1004. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 451726 (pause) in control group while starting unit. Ignoring.
  1005. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  1006. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452109 (pause) in control group while starting unit. Ignoring.
  1007. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  1008. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452295 (pause) in control group while starting unit. Ignoring.
  1009. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  1010. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452280 (pause) in control group while starting unit. Ignoring.
  1011. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  1012. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452272 (tini) in control group while starting unit. Ignoring.
  1013. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  1014. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452375 (toolbox.sh) in control group while starting unit. Ignoring.
  1015. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  1016. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 2179753 (sleep) in control group while starting unit. Ignoring.
  1017. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  1018. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 452642 (ceph-mds) in control group while starting unit. Ignoring.
  1019. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  1020. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 453022 (ceph-mds) in control group while starting unit. Ignoring.
  1021. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  1022. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 453017 (ceph-mgr) in control group while starting unit. Ignoring.
  1023. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  1024. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 455348 (pause) in control group while starting unit. Ignoring.
  1025. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  1026. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Found left-over process 455791 (ceph-crash) in control group while starting unit. Ignoring.
  1027. Dec 02 03:15:41 k8s-node0 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
  1028. Dec 02 03:15:41 k8s-node0 containerd[2179758]: containerd: invalid disabled plugin URI "restart" expect io.containerd.x.vx
  1029. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Main process exited, code=exited, status=1/FAILURE
  1030. -- Subject: Unit process exited
  1031. -- Defined-By: systemd
  1032. -- Support: http://www.ubuntu.com/support
  1033. --
  1034. -- An ExecStart= process belonging to unit containerd.service has exited.
  1035. --
  1036. -- The process' exit code is 'exited' and its exit status is 1.
  1037. Dec 02 03:15:41 k8s-node0 systemd[1]: containerd.service: Failed with result 'exit-code'.
  1038. -- Subject: Unit failed
  1039. -- Defined-By: systemd
  1040. -- Support: http://www.ubuntu.com/support
  1041. --
  1042. -- The unit containerd.service has entered the 'failed' state with result 'exit-code'.
  1043. Dec 02 03:15:41 k8s-node0 systemd[1]: Failed to start containerd container runtime.
  1044. -- Subject: A start job for unit containerd.service has failed
  1045. -- Defined-By: systemd
  1046. -- Support: http://www.ubuntu.com/support
  1047. --
  1048. -- A start job for unit containerd.service has finished with a failure.
  1049. --
  1050. -- The job identifier is 11855 and the job result is failed.
  1051. Dec 02 03:15:42 k8s-node0 kubelet[4427]: E1202 03:15:42.148799 4427 remote_runtime.go:207] "ListPodSandbox with filter from runtime service failed" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\"" filter="nil"
  1052. Dec 02 03:15:42 k8s-node0 kubelet[4427]: E1202 03:15:42.148866 4427 kuberuntime_sandbox.go:223] "Failed to list pod sandboxes" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  1053. Dec 02 03:15:42 k8s-node0 kubelet[4427]: E1202 03:15:42.148910 4427 generic.go:205] "GenericPLEG: Unable to retrieve pods" err="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\""
  1054. Dec 02 03:15:42 k8s-node0 kubelet[4427]: I1202 03:15:42.310488 4427 balancer_conn_wrappers.go:78] pickfirstBalancer: HandleSubConnStateChange: 0xc0001bd780, {CONNECTING <nil>}
  1055. Dec 02 03:15:42 k8s-node0 kubelet[4427]: W1202 03:15:42.310499 4427 clientconn.go:1223] grpc: addrConn.createTransport failed to connect to {/var/run/containerd/containerd.sock <nil> 0 <nil>}. Err :connection error: desc = "transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory". Reconnecting...
  1056. Dec 02 03:15:42 k8s-node0 kubelet[4427]: I1202 03:15:42.310603 4427 balancer_conn_wrappers.go:78] pickfirstBalancer: HandleSubConnStateChange: 0xc0001bd780, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory"}
  1057. Dec 02 03:15:42 k8s-node0 kubelet[4427]: I1202 03:15:42.328356 4427 balancer_conn_wrappers.go:78] pickfirstBalancer: HandleSubConnStateChange: 0xc0001bd910, {CONNECTING <nil>}
  1058. Dec 02 03:15:42 k8s-node0 kubelet[4427]: W1202 03:15:42.328376 4427 clientconn.go:1223] grpc: addrConn.createTransport failed to connect to {/var/run/containerd/containerd.sock <nil> 0 <nil>}. Err :connection error: desc = "transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory". Reconnecting...
  1059. Dec 02 03:15:42 k8s-node0 kubelet[4427]: I1202 03:15:42.328459 4427 balancer_conn_wrappers.go:78] pickfirstBalancer: HandleSubConnStateChange: 0xc0001bd910, {TRANSIENT_FAILURE connection error: desc = "transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory"}
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!