Advertisement
Guest User

k3s logs

a guest
Jun 27th, 2022
40
0
85 days
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
Bash 22.05 KB | None | 0 0
  1. root@ava:~# journalctl -xe
  2. [...]
  3. Jun 27 09:16:14 ava systemd[1]: k3s.service: Scheduled restart job, restart counter is at 5.
  4. -- Subject: Automatic restarting of a unit has been scheduled
  5. -- Defined-By: systemd
  6. -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
  7. --
  8. -- Automatic restarting of the unit k3s.service has been scheduled, as the result for
  9. -- the configured Restart= setting for the unit.
  10. Jun 27 09:16:14 ava systemd[1]: Stopped Lightweight Kubernetes.
  11. -- Subject: A stop job for unit k3s.service has finished
  12. -- Defined-By: systemd
  13. -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
  14. --
  15. -- A stop job for unit k3s.service has finished.
  16. --
  17. -- The job identifier is 424 and the job result is done.
  18. Jun 27 09:16:14 ava systemd[1]: Starting Lightweight Kubernetes...
  19. -- Subject: A start job for unit k3s.service has begun execution
  20. -- Defined-By: systemd
  21. -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
  22. --
  23. -- A start job for unit k3s.service has begun execution.
  24. --
  25. -- The job identifier is 424.
  26. Jun 27 09:16:14 ava sh[823]: + systemctl is-enabled --quiet nm-cloud-setup.service
  27. Jun 27 09:16:14 ava sh[824]: Failed to get unit file state for nm-cloud-setup.service: No such file or directory
  28. Jun 27 09:16:15 ava k3s[827]: time="2022-06-27T09:16:15Z" level=info msg="Starting k3s v1.22.6+k3s1+git4262c6b91a43ef8411870f72ff8b8715949f90e2 (4262c6b9)"
  29. Jun 27 09:16:15 ava k3s[827]: time="2022-06-27T09:16:15Z" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
  30. Jun 27 09:16:15 ava k3s[827]: time="2022-06-27T09:16:15Z" level=info msg="Configuring database table schema and indexes, this may take a moment..."
  31. Jun 27 09:16:15 ava k3s[827]: time="2022-06-27T09:16:15Z" level=info msg="Database tables and indexes are up to date"
  32. Jun 27 09:16:15 ava k3s[827]: time="2022-06-27T09:16:15Z" level=info msg="Kine available at unix://kine.sock"
  33. Jun 27 09:16:15 ava k3s[827]: time="2022-06-27T09:16:15Z" level=info msg="Reconciling bootstrap data between datastore and disk"
  34. Jun 27 09:16:15 ava k3s[827]: time="2022-06-27T09:16:15Z" level=info msg="Running kube-apiserver --advertise-port=6443 --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,k3s --authorization-mode=Node,RBAC --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/k3s/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/k3s/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction --etcd-servers=unix://kine.sock --feature-gates=JobTrackingWithFinalizers=true --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/k3s/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/k3s/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/k3s/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/k3s/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/k3s/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/k3s/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6444 --service-account-issuer=https://kubernetes.default.svc.cluster.local --service-account-key-file=/var/lib/rancher/k3s/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/k3s/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --service-node-port-range=30000-32767 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
  35. Jun 27 09:16:15 ava k3s[827]: Flag --insecure-port has been deprecated, This flag has no effect now and will be removed in v1.24.
  36. Jun 27 09:16:15 ava k3s[827]: I0627 09:16:15.077716     827 server.go:581] external host was not specified, using 10.1.194.29
  37. Jun 27 09:16:15 ava k3s[827]: I0627 09:16:15.078083     827 server.go:175] Version: v1.22.6-k3s1
  38. Jun 27 09:16:15 ava k3s[827]: time="2022-06-27T09:16:15Z" level=info msg="Running kube-scheduler --authentication-kubeconfig=/var/lib/rancher/k3s/server/cred/scheduler.kubeconfig --authorization-kubeconfig=/var/lib/rancher/k3s/server/cred/scheduler.kubeconfig --bind-address=127.0.0.1 --kubeconfig=/var/lib/rancher/k3s/server/cred/scheduler.kubeconfig --leader-elect=false --profiling=false --secure-port=10259"
  39. Jun 27 09:16:15 ava k3s[827]: time="2022-06-27T09:16:15Z" level=info msg="Waiting for API server to become available"
  40. Jun 27 09:16:15 ava k3s[827]: time="2022-06-27T09:16:15Z" level=info msg="Running kube-controller-manager --allocate-node-cidrs=true --authentication-kubeconfig=/var/lib/rancher/k3s/server/cred/controller.kubeconfig --authorization-kubeconfig=/var/lib/rancher/k3s/server/cred/controller.kubeconfig --bind-address=127.0.0.1 --cluster-cidr=10.42.0.0/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/k3s/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/k3s/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/k3s/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/k3s/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/k3s/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/k3s/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --feature-gates=JobTrackingWithFinalizers=true --kubeconfig=/var/lib/rancher/k3s/server/cred/controller.kubeconfig --leader-elect=false --profiling=false --root-ca-file=/var/lib/rancher/k3s/server/tls/server-ca.crt --secure-port=10257 --service-account-private-key-file=/var/lib/rancher/k3s/server/tls/service.key --use-service-account-credentials=true"
  41. Jun 27 09:16:15 ava k3s[827]: time="2022-06-27T09:16:15Z" level=info msg="Running cloud-controller-manager --allocate-node-cidrs=true --authentication-kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --authorization-kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --bind-address=127.0.0.1 --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --node-status-update-frequency=1m0s --port=0 --profiling=false"
  42. Jun 27 09:16:15 ava k3s[827]: time="2022-06-27T09:16:15Z" level=info msg="Node token is available at /var/lib/rancher/k3s/server/token"
  43. Jun 27 09:16:15 ava k3s[827]: time="2022-06-27T09:16:15Z" level=info msg="To join node to cluster: k3s agent -s https://10.1.194.29:6443 -t ${NODE_TOKEN}"' exit code is 'exited' and its exit status is 2.
  44. Jun 27 09:16:15 ava systemd[1]: k3s.service: Failed with result 'exit-code'.
  45. -- Subject: Unit failed
  46. -- Defined-By: systemd
  47. -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
  48. --
  49. -- The unit k3s.service has entered the 'failed' state with result 'exit-code'.
  50. Jun 27 09:16:15 ava systemd[1]: Failed to start Lightweight Kubernetes.
  51. -- Subject: A start job for unit k3s.service has failed
  52. -- Defined-By: systemd
  53. -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
  54. --
  55. -- A start job for unit k3s.service has finished with a failure.
  56. --
  57. -- The job identifier is 424 and the job result is failed.
  58. Jun 27 09:20:28 ava systemd-resolved[503]: Clock change detected. Flushing caches.
  59. Jun 27 09:20:28 ava systemd-timesyncd[507]: Contacted time server 216.239.35.8:123 (time3.google.com).
  60. Jun 27 09:20:28 ava systemd-timesyncd[507]: Initial clock synchronization to Mon 2022-06-27 09:20:28.113165 UTC.
  61. -- Subject: Initial clock synchronization
  62. -- Defined-By: systemd
  63. -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
  64. --
  65. -- For the first time during the current boot an NTP synchronization has been
  66. -- acquired and the local system clock adjustment has been initiated.
  67. root@ava:~# systemctl status k3s.service
  68. * k3s.service - Lightweight Kubernetes
  69.     Loaded: loaded (/lib/systemd/system/k3s.service; enabled; vendor preset: enabled)
  70.     Active: activating (auto-restart) (Result: exit-code) since Mon 2022-06-27 09:24:56 UTC; 4s ago
  71.       Docs: https://k3s.io
  72.    Process: 2965 ExecStartPre=/bin/sh -xc ! systemctl is-enabled --quiet nm-cloud-setup.service (code=exited, status=0/SUCCESS)
  73.    Process: 2967 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS)
  74.    Process: 2968 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
  75.    Process: 2969 ExecStart=/usr/local/bin/k3s server (code=exited, status=2)
  76.    Process: 3007 ExecStopPost=/bin/sh -c if systemctl is-system-running | grep -i                             'stopping'; then /usr/local/bin/k3s-killall.sh; fi (code=exited, status=0/SUCCESS)
  77.   Main PID: 2969 (code=exited, status=2)
  78.  
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement