k9casca2/k3s-ansible-copia/error

mar 12 16:33:27 CASCA k3s[293286]: I0312 16:33:27.059914  293286 server.go:150] Version: v1.31.6+k3s1
mar 12 16:33:27 CASCA k3s[293286]: I0312 16:33:27.059934  293286 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:33:27 CASCA k3s[293286]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:33:27 CASCA k3s[293286]: time="2025-03-12T16:33:27+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:33:27 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:33:27 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:33:27 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 114527 and the job result is failed.
mar 12 16:33:32 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1191.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:33:32 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 114621 and the job result is done.
mar 12 16:33:32 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 114621.
mar 12 16:33:32 CASCA sh[293679]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:33:32 CASCA k3s[293686]: time="2025-03-12T16:33:32+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:33:32 CASCA k3s[293686]: time="2025-03-12T16:33:32+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:33:32 CASCA k3s[293686]: time="2025-03-12T16:33:32+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:33:32 CASCA k3s[293686]: time="2025-03-12T16:33:32+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:33:32 CASCA k3s[293686]: time="2025-03-12T16:33:32+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:33:32 CASCA k3s[293686]: time="2025-03-12T16:33:32+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:33:32 CASCA k3s[293686]: time="2025-03-12T16:33:32+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:33:32 CASCA k3s[293686]: time="2025-03-12T16:33:32+01:00" 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"
mar 12 16:33:32 CASCA k3s[293686]: W0312 16:33:32.541730  293686 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:33:32 CASCA k3s[293686]: time="2025-03-12T16:33:32+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:33:32 CASCA k3s[293686]: time="2025-03-12T16:33:32+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:33:32 CASCA k3s[293686]: W0312 16:33:32.542188  293686 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:33:32 CASCA k3s[293686]: I0312 16:33:32.542231  293686 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:33:32 CASCA k3s[293686]: time="2025-03-12T16:33:32+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:33:32 CASCA k3s[293686]: time="2025-03-12T16:33:32+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:33:32 CASCA k3s[293686]: time="2025-03-12T16:33:32+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:33:32 CASCA k3s[293686]: time="2025-03-12T16:33:32+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:33:32 CASCA k3s[293686]: time="2025-03-12T16:33:32+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:33:32 CASCA k3s[293686]: I0312 16:33:32.543427  293686 server.go:150] Version: v1.31.6+k3s1
mar 12 16:33:32 CASCA k3s[293686]: I0312 16:33:32.543446  293686 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:33:32 CASCA k3s[293686]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:33:32 CASCA k3s[293686]: time="2025-03-12T16:33:32+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:33:32 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:33:32 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:33:32 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 114621 and the job result is failed.
mar 12 16:33:37 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1192.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:33:37 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 114715 and the job result is done.
mar 12 16:33:37 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 114715.
mar 12 16:33:37 CASCA sh[294117]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:33:37 CASCA k3s[294128]: time="2025-03-12T16:33:37+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:33:37 CASCA k3s[294128]: time="2025-03-12T16:33:37+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:33:37 CASCA k3s[294128]: time="2025-03-12T16:33:37+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:33:37 CASCA k3s[294128]: time="2025-03-12T16:33:37+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:33:37 CASCA k3s[294128]: time="2025-03-12T16:33:37+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:33:37 CASCA k3s[294128]: time="2025-03-12T16:33:37+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:33:38 CASCA k3s[294128]: time="2025-03-12T16:33:38+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:33:38 CASCA k3s[294128]: time="2025-03-12T16:33:38+01:00" 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"
mar 12 16:33:38 CASCA k3s[294128]: W0312 16:33:38.053193  294128 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:33:38 CASCA k3s[294128]: I0312 16:33:38.053734  294128 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:33:38 CASCA k3s[294128]: time="2025-03-12T16:33:38+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:33:38 CASCA k3s[294128]: time="2025-03-12T16:33:38+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:33:38 CASCA k3s[294128]: W0312 16:33:38.054080  294128 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:33:38 CASCA k3s[294128]: time="2025-03-12T16:33:38+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:33:38 CASCA k3s[294128]: time="2025-03-12T16:33:38+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:33:38 CASCA k3s[294128]: I0312 16:33:38.054960  294128 server.go:150] Version: v1.31.6+k3s1
mar 12 16:33:38 CASCA k3s[294128]: I0312 16:33:38.054974  294128 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:33:38 CASCA k3s[294128]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:33:38 CASCA k3s[294128]: time="2025-03-12T16:33:38+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:33:38 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:33:38 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:33:38 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 114715 and the job result is failed.
mar 12 16:33:43 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1193.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:33:43 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 114809 and the job result is done.
mar 12 16:33:43 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 114809.
mar 12 16:33:43 CASCA sh[294592]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:33:43 CASCA k3s[294599]: time="2025-03-12T16:33:43+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:33:43 CASCA k3s[294599]: time="2025-03-12T16:33:43+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:33:43 CASCA k3s[294599]: time="2025-03-12T16:33:43+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:33:43 CASCA k3s[294599]: time="2025-03-12T16:33:43+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:33:43 CASCA k3s[294599]: time="2025-03-12T16:33:43+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:33:43 CASCA k3s[294599]: time="2025-03-12T16:33:43+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:33:43 CASCA k3s[294599]: time="2025-03-12T16:33:43+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:33:43 CASCA k3s[294599]: time="2025-03-12T16:33:43+01:00" 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"
mar 12 16:33:43 CASCA k3s[294599]: time="2025-03-12T16:33:43+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:33:43 CASCA k3s[294599]: W0312 16:33:43.564110  294599 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:33:43 CASCA k3s[294599]: time="2025-03-12T16:33:43+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:33:43 CASCA k3s[294599]: W0312 16:33:43.564646  294599 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:33:43 CASCA k3s[294599]: I0312 16:33:43.564753  294599 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:33:43 CASCA k3s[294599]: time="2025-03-12T16:33:43+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:33:43 CASCA k3s[294599]: time="2025-03-12T16:33:43+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:33:43 CASCA k3s[294599]: time="2025-03-12T16:33:43+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:33:43 CASCA k3s[294599]: time="2025-03-12T16:33:43+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:33:43 CASCA k3s[294599]: time="2025-03-12T16:33:43+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:33:43 CASCA k3s[294599]: I0312 16:33:43.566007  294599 server.go:150] Version: v1.31.6+k3s1
mar 12 16:33:43 CASCA k3s[294599]: I0312 16:33:43.566030  294599 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:33:43 CASCA k3s[294599]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:33:43 CASCA k3s[294599]: time="2025-03-12T16:33:43+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:33:43 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:33:43 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:33:43 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 114809 and the job result is failed.
mar 12 16:33:48 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1194.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:33:48 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 114903 and the job result is done.
mar 12 16:33:48 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 114903.
mar 12 16:33:48 CASCA sh[294930]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:33:48 CASCA k3s[294940]: time="2025-03-12T16:33:48+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:33:48 CASCA k3s[294940]: time="2025-03-12T16:33:48+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:33:48 CASCA k3s[294940]: time="2025-03-12T16:33:48+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:33:48 CASCA k3s[294940]: time="2025-03-12T16:33:48+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:33:48 CASCA k3s[294940]: time="2025-03-12T16:33:48+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:33:48 CASCA k3s[294940]: time="2025-03-12T16:33:48+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:33:49 CASCA k3s[294940]: time="2025-03-12T16:33:49+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:33:49 CASCA k3s[294940]: time="2025-03-12T16:33:49+01:00" 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"
mar 12 16:33:49 CASCA k3s[294940]: time="2025-03-12T16:33:49+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:33:49 CASCA k3s[294940]: W0312 16:33:49.054677  294940 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:33:49 CASCA k3s[294940]: time="2025-03-12T16:33:49+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:33:49 CASCA k3s[294940]: W0312 16:33:49.055025  294940 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:33:49 CASCA k3s[294940]: time="2025-03-12T16:33:49+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:33:49 CASCA k3s[294940]: time="2025-03-12T16:33:49+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:33:49 CASCA k3s[294940]: I0312 16:33:49.055856  294940 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:33:49 CASCA k3s[294940]: time="2025-03-12T16:33:49+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:33:49 CASCA k3s[294940]: time="2025-03-12T16:33:49+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:33:49 CASCA k3s[294940]: time="2025-03-12T16:33:49+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:33:49 CASCA k3s[294940]: time="2025-03-12T16:33:49+01:00" level=info msg="Wrote kubeconfig /etc/rancher/k3s/k3s.yaml"
mar 12 16:33:49 CASCA k3s[294940]: time="2025-03-12T16:33:49+01:00" level=info msg="Run: k3s kubectl"
mar 12 16:33:49 CASCA k3s[294940]: I0312 16:33:49.057084  294940 server.go:150] Version: v1.31.6+k3s1
mar 12 16:33:49 CASCA k3s[294940]: I0312 16:33:49.057104  294940 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:33:49 CASCA k3s[294940]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:33:49 CASCA k3s[294940]: time="2025-03-12T16:33:49+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:33:49 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:33:49 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:33:49 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 114903 and the job result is failed.
mar 12 16:33:54 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1195.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:33:54 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 114997 and the job result is done.
mar 12 16:33:54 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 114997.
mar 12 16:33:54 CASCA sh[295357]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:33:54 CASCA k3s[295365]: time="2025-03-12T16:33:54+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:33:54 CASCA k3s[295365]: time="2025-03-12T16:33:54+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:33:54 CASCA k3s[295365]: time="2025-03-12T16:33:54+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:33:54 CASCA k3s[295365]: time="2025-03-12T16:33:54+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:33:54 CASCA k3s[295365]: time="2025-03-12T16:33:54+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:33:54 CASCA k3s[295365]: time="2025-03-12T16:33:54+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:33:54 CASCA k3s[295365]: time="2025-03-12T16:33:54+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:33:54 CASCA k3s[295365]: time="2025-03-12T16:33:54+01:00" 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"
mar 12 16:33:54 CASCA k3s[295365]: W0312 16:33:54.580835  295365 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:33:54 CASCA k3s[295365]: time="2025-03-12T16:33:54+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:33:54 CASCA k3s[295365]: time="2025-03-12T16:33:54+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:33:54 CASCA k3s[295365]: W0312 16:33:54.581307  295365 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:33:54 CASCA k3s[295365]: I0312 16:33:54.581333  295365 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:33:54 CASCA k3s[295365]: time="2025-03-12T16:33:54+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:33:54 CASCA k3s[295365]: time="2025-03-12T16:33:54+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:33:54 CASCA k3s[295365]: time="2025-03-12T16:33:54+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:33:54 CASCA k3s[295365]: time="2025-03-12T16:33:54+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:33:54 CASCA k3s[295365]: time="2025-03-12T16:33:54+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:33:54 CASCA k3s[295365]: I0312 16:33:54.582544  295365 server.go:150] Version: v1.31.6+k3s1
mar 12 16:33:54 CASCA k3s[295365]: I0312 16:33:54.582565  295365 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:33:54 CASCA k3s[295365]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:33:54 CASCA k3s[295365]: time="2025-03-12T16:33:54+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:33:54 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:33:54 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:33:54 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 114997 and the job result is failed.
mar 12 16:33:59 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1196.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:33:59 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 115091 and the job result is done.
mar 12 16:33:59 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 115091.
mar 12 16:33:59 CASCA sh[295816]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:33:59 CASCA k3s[295825]: time="2025-03-12T16:33:59+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:33:59 CASCA k3s[295825]: time="2025-03-12T16:33:59+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:33:59 CASCA k3s[295825]: time="2025-03-12T16:33:59+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:33:59 CASCA k3s[295825]: time="2025-03-12T16:33:59+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:33:59 CASCA k3s[295825]: time="2025-03-12T16:33:59+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:33:59 CASCA k3s[295825]: time="2025-03-12T16:33:59+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:34:00 CASCA k3s[295825]: time="2025-03-12T16:34:00+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:34:00 CASCA k3s[295825]: time="2025-03-12T16:34:00+01:00" 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"
mar 12 16:34:00 CASCA k3s[295825]: W0312 16:34:00.043113  295825 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:00 CASCA k3s[295825]: time="2025-03-12T16:34:00+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:34:00 CASCA k3s[295825]: time="2025-03-12T16:34:00+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:34:00 CASCA k3s[295825]: W0312 16:34:00.043461  295825 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:00 CASCA k3s[295825]: I0312 16:34:00.043592  295825 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:34:00 CASCA k3s[295825]: time="2025-03-12T16:34:00+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:34:00 CASCA k3s[295825]: time="2025-03-12T16:34:00+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:34:00 CASCA k3s[295825]: time="2025-03-12T16:34:00+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:34:00 CASCA k3s[295825]: time="2025-03-12T16:34:00+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:34:00 CASCA k3s[295825]: time="2025-03-12T16:34:00+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:34:00 CASCA k3s[295825]: I0312 16:34:00.044831  295825 server.go:150] Version: v1.31.6+k3s1
mar 12 16:34:00 CASCA k3s[295825]: I0312 16:34:00.044845  295825 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:34:00 CASCA k3s[295825]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:34:00 CASCA k3s[295825]: time="2025-03-12T16:34:00+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:34:00 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:34:00 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:34:00 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 115091 and the job result is failed.
mar 12 16:34:03 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 115185 and the job result is done.
mar 12 16:34:03 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 115185.
mar 12 16:34:03 CASCA sh[296083]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:34:03 CASCA k3s[296088]: time="2025-03-12T16:34:03+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:34:03 CASCA k3s[296088]: time="2025-03-12T16:34:03+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:34:03 CASCA k3s[296088]: time="2025-03-12T16:34:03+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:34:03 CASCA k3s[296088]: time="2025-03-12T16:34:03+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:34:03 CASCA k3s[296088]: time="2025-03-12T16:34:03+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:34:03 CASCA k3s[296088]: time="2025-03-12T16:34:03+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:34:03 CASCA k3s[296088]: time="2025-03-12T16:34:03+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:34:03 CASCA k3s[296088]: time="2025-03-12T16:34:03+01:00" 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"
mar 12 16:34:03 CASCA k3s[296088]: time="2025-03-12T16:34:03+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:34:03 CASCA k3s[296088]: W0312 16:34:03.971970  296088 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:03 CASCA k3s[296088]: time="2025-03-12T16:34:03+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:34:03 CASCA k3s[296088]: W0312 16:34:03.972430  296088 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:03 CASCA k3s[296088]: I0312 16:34:03.972518  296088 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:34:03 CASCA k3s[296088]: time="2025-03-12T16:34:03+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:34:03 CASCA k3s[296088]: time="2025-03-12T16:34:03+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:34:03 CASCA k3s[296088]: time="2025-03-12T16:34:03+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:34:03 CASCA k3s[296088]: time="2025-03-12T16:34:03+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:34:03 CASCA k3s[296088]: time="2025-03-12T16:34:03+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:34:03 CASCA k3s[296088]: I0312 16:34:03.973720  296088 server.go:150] Version: v1.31.6+k3s1
mar 12 16:34:03 CASCA k3s[296088]: I0312 16:34:03.973739  296088 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:34:03 CASCA k3s[296088]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:34:03 CASCA k3s[296088]: time="2025-03-12T16:34:03+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:34:03 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:34:03 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:34:03 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 115185 and the job result is failed.
mar 12 16:34:09 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1197.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:34:09 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 115279 and the job result is done.
mar 12 16:34:09 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 115279.
mar 12 16:34:09 CASCA sh[296535]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:34:09 CASCA k3s[296543]: time="2025-03-12T16:34:09+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:34:09 CASCA k3s[296543]: time="2025-03-12T16:34:09+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:34:09 CASCA k3s[296543]: time="2025-03-12T16:34:09+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:34:09 CASCA k3s[296543]: time="2025-03-12T16:34:09+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:34:09 CASCA k3s[296543]: time="2025-03-12T16:34:09+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:34:09 CASCA k3s[296543]: time="2025-03-12T16:34:09+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:34:09 CASCA k3s[296543]: time="2025-03-12T16:34:09+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:34:09 CASCA k3s[296543]: time="2025-03-12T16:34:09+01:00" 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"
mar 12 16:34:09 CASCA k3s[296543]: W0312 16:34:09.307627  296543 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:09 CASCA k3s[296543]: time="2025-03-12T16:34:09+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:34:09 CASCA k3s[296543]: time="2025-03-12T16:34:09+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:34:09 CASCA k3s[296543]: W0312 16:34:09.307971  296543 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:09 CASCA k3s[296543]: time="2025-03-12T16:34:09+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:34:09 CASCA k3s[296543]: I0312 16:34:09.308180  296543 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:34:09 CASCA k3s[296543]: time="2025-03-12T16:34:09+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:34:09 CASCA k3s[296543]: time="2025-03-12T16:34:09+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:34:09 CASCA k3s[296543]: time="2025-03-12T16:34:09+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:34:09 CASCA k3s[296543]: time="2025-03-12T16:34:09+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:34:09 CASCA k3s[296543]: I0312 16:34:09.309421  296543 server.go:150] Version: v1.31.6+k3s1
mar 12 16:34:09 CASCA k3s[296543]: I0312 16:34:09.309437  296543 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:34:09 CASCA k3s[296543]: time="2025-03-12T16:34:09+01:00" level=info msg="Wrote kubeconfig /etc/rancher/k3s/k3s.yaml"
mar 12 16:34:09 CASCA k3s[296543]: time="2025-03-12T16:34:09+01:00" level=info msg="Run: k3s kubectl"
mar 12 16:34:09 CASCA k3s[296543]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:34:09 CASCA k3s[296543]: time="2025-03-12T16:34:09+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:34:09 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:34:09 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:34:09 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 115279 and the job result is failed.
mar 12 16:34:14 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1198.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:34:14 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 115373 and the job result is done.
mar 12 16:34:14 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 115373.
mar 12 16:34:14 CASCA sh[296970]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:34:14 CASCA k3s[296980]: time="2025-03-12T16:34:14+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:34:14 CASCA k3s[296980]: time="2025-03-12T16:34:14+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:34:14 CASCA k3s[296980]: time="2025-03-12T16:34:14+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:34:14 CASCA k3s[296980]: time="2025-03-12T16:34:14+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:34:14 CASCA k3s[296980]: time="2025-03-12T16:34:14+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:34:14 CASCA k3s[296980]: time="2025-03-12T16:34:14+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:34:14 CASCA k3s[296980]: time="2025-03-12T16:34:14+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:34:14 CASCA k3s[296980]: time="2025-03-12T16:34:14+01:00" 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"
mar 12 16:34:14 CASCA k3s[296980]: time="2025-03-12T16:34:14+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:34:14 CASCA k3s[296980]: W0312 16:34:14.835858  296980 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:14 CASCA k3s[296980]: time="2025-03-12T16:34:14+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:34:14 CASCA k3s[296980]: W0312 16:34:14.836194  296980 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:14 CASCA k3s[296980]: time="2025-03-12T16:34:14+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:34:14 CASCA k3s[296980]: time="2025-03-12T16:34:14+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:34:14 CASCA k3s[296980]: I0312 16:34:14.837054  296980 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:34:14 CASCA k3s[296980]: time="2025-03-12T16:34:14+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:34:14 CASCA k3s[296980]: time="2025-03-12T16:34:14+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:34:14 CASCA k3s[296980]: time="2025-03-12T16:34:14+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:34:14 CASCA k3s[296980]: time="2025-03-12T16:34:14+01:00" level=info msg="Wrote kubeconfig /etc/rancher/k3s/k3s.yaml"
mar 12 16:34:14 CASCA k3s[296980]: time="2025-03-12T16:34:14+01:00" level=info msg="Run: k3s kubectl"
mar 12 16:34:14 CASCA k3s[296980]: I0312 16:34:14.838251  296980 server.go:150] Version: v1.31.6+k3s1
mar 12 16:34:14 CASCA k3s[296980]: I0312 16:34:14.838274  296980 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:34:14 CASCA k3s[296980]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:34:14 CASCA k3s[296980]: time="2025-03-12T16:34:14+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:34:14 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:34:14 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:34:14 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 115373 and the job result is failed.
mar 12 16:34:20 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1199.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:34:20 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 115467 and the job result is done.
mar 12 16:34:20 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 115467.
mar 12 16:34:20 CASCA sh[297349]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:34:20 CASCA k3s[297356]: time="2025-03-12T16:34:20+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:34:20 CASCA k3s[297356]: time="2025-03-12T16:34:20+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:34:20 CASCA k3s[297356]: time="2025-03-12T16:34:20+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:34:20 CASCA k3s[297356]: time="2025-03-12T16:34:20+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:34:20 CASCA k3s[297356]: time="2025-03-12T16:34:20+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:34:20 CASCA k3s[297356]: time="2025-03-12T16:34:20+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:34:20 CASCA k3s[297356]: time="2025-03-12T16:34:20+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:34:20 CASCA k3s[297356]: time="2025-03-12T16:34:20+01:00" 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"
mar 12 16:34:20 CASCA k3s[297356]: W0312 16:34:20.345215  297356 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:20 CASCA k3s[297356]: time="2025-03-12T16:34:20+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:34:20 CASCA k3s[297356]: time="2025-03-12T16:34:20+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:34:20 CASCA k3s[297356]: W0312 16:34:20.345563  297356 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:20 CASCA k3s[297356]: time="2025-03-12T16:34:20+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:34:20 CASCA k3s[297356]: I0312 16:34:20.345751  297356 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:34:20 CASCA k3s[297356]: time="2025-03-12T16:34:20+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:34:20 CASCA k3s[297356]: time="2025-03-12T16:34:20+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:34:20 CASCA k3s[297356]: time="2025-03-12T16:34:20+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:34:20 CASCA k3s[297356]: time="2025-03-12T16:34:20+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:34:20 CASCA k3s[297356]: I0312 16:34:20.346957  297356 server.go:150] Version: v1.31.6+k3s1
mar 12 16:34:20 CASCA k3s[297356]: I0312 16:34:20.346976  297356 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:34:20 CASCA k3s[297356]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:34:20 CASCA k3s[297356]: time="2025-03-12T16:34:20+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:34:20 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:34:20 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:34:20 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 115467 and the job result is failed.
mar 12 16:34:25 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1200.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:34:25 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 115561 and the job result is done.
mar 12 16:34:25 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 115561.
mar 12 16:34:25 CASCA sh[297733]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:34:25 CASCA k3s[297740]: time="2025-03-12T16:34:25+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:34:25 CASCA k3s[297740]: time="2025-03-12T16:34:25+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:34:25 CASCA k3s[297740]: time="2025-03-12T16:34:25+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:34:25 CASCA k3s[297740]: time="2025-03-12T16:34:25+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:34:25 CASCA k3s[297740]: time="2025-03-12T16:34:25+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:34:25 CASCA k3s[297740]: time="2025-03-12T16:34:25+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:34:25 CASCA k3s[297740]: time="2025-03-12T16:34:25+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:34:25 CASCA k3s[297740]: time="2025-03-12T16:34:25+01:00" 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"
mar 12 16:34:25 CASCA k3s[297740]: W0312 16:34:25.856973  297740 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:25 CASCA k3s[297740]: time="2025-03-12T16:34:25+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:34:25 CASCA k3s[297740]: time="2025-03-12T16:34:25+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:34:25 CASCA k3s[297740]: W0312 16:34:25.857380  297740 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:25 CASCA k3s[297740]: time="2025-03-12T16:34:25+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:34:25 CASCA k3s[297740]: time="2025-03-12T16:34:25+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:34:25 CASCA k3s[297740]: time="2025-03-12T16:34:25+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:34:25 CASCA k3s[297740]: time="2025-03-12T16:34:25+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:34:25 CASCA k3s[297740]: I0312 16:34:25.858380  297740 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:34:25 CASCA k3s[297740]: time="2025-03-12T16:34:25+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:34:25 CASCA k3s[297740]: time="2025-03-12T16:34:25+01:00" level=info msg="Wrote kubeconfig /etc/rancher/k3s/k3s.yaml"
mar 12 16:34:25 CASCA k3s[297740]: time="2025-03-12T16:34:25+01:00" level=info msg="Run: k3s kubectl"
mar 12 16:34:25 CASCA k3s[297740]: I0312 16:34:25.859623  297740 server.go:150] Version: v1.31.6+k3s1
mar 12 16:34:25 CASCA k3s[297740]: I0312 16:34:25.859637  297740 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:34:25 CASCA k3s[297740]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:34:25 CASCA k3s[297740]: time="2025-03-12T16:34:25+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:34:25 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:34:25 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:34:25 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 115561 and the job result is failed.
mar 12 16:34:31 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1201.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:34:31 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 115655 and the job result is done.
mar 12 16:34:31 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 115655.
mar 12 16:34:31 CASCA sh[298138]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:34:31 CASCA k3s[298148]: time="2025-03-12T16:34:31+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:34:31 CASCA k3s[298148]: time="2025-03-12T16:34:31+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:34:31 CASCA k3s[298148]: time="2025-03-12T16:34:31+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:34:31 CASCA k3s[298148]: time="2025-03-12T16:34:31+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:34:31 CASCA k3s[298148]: time="2025-03-12T16:34:31+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:34:31 CASCA k3s[298148]: time="2025-03-12T16:34:31+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:34:31 CASCA k3s[298148]: time="2025-03-12T16:34:31+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:34:31 CASCA k3s[298148]: time="2025-03-12T16:34:31+01:00" 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"
mar 12 16:34:31 CASCA k3s[298148]: W0312 16:34:31.292453  298148 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:31 CASCA k3s[298148]: time="2025-03-12T16:34:31+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:34:31 CASCA k3s[298148]: time="2025-03-12T16:34:31+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:34:31 CASCA k3s[298148]: W0312 16:34:31.292799  298148 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:31 CASCA k3s[298148]: I0312 16:34:31.292948  298148 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:34:31 CASCA k3s[298148]: time="2025-03-12T16:34:31+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:34:31 CASCA k3s[298148]: time="2025-03-12T16:34:31+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:34:31 CASCA k3s[298148]: time="2025-03-12T16:34:31+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:34:31 CASCA k3s[298148]: time="2025-03-12T16:34:31+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:34:31 CASCA k3s[298148]: time="2025-03-12T16:34:31+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:34:31 CASCA k3s[298148]: I0312 16:34:31.294174  298148 server.go:150] Version: v1.31.6+k3s1
mar 12 16:34:31 CASCA k3s[298148]: I0312 16:34:31.294191  298148 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:34:31 CASCA k3s[298148]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:34:31 CASCA k3s[298148]: time="2025-03-12T16:34:31+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:34:31 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:34:31 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:34:31 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 115655 and the job result is failed.
mar 12 16:34:36 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1202.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:34:36 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 115749 and the job result is done.
mar 12 16:34:36 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 115749.
mar 12 16:34:36 CASCA sh[298547]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:34:36 CASCA k3s[298557]: time="2025-03-12T16:34:36+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:34:36 CASCA k3s[298557]: time="2025-03-12T16:34:36+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:34:36 CASCA k3s[298557]: time="2025-03-12T16:34:36+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:34:36 CASCA k3s[298557]: time="2025-03-12T16:34:36+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:34:36 CASCA k3s[298557]: time="2025-03-12T16:34:36+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:34:36 CASCA k3s[298557]: time="2025-03-12T16:34:36+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:34:36 CASCA k3s[298557]: time="2025-03-12T16:34:36+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:34:36 CASCA k3s[298557]: time="2025-03-12T16:34:36+01:00" 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"
mar 12 16:34:36 CASCA k3s[298557]: W0312 16:34:36.831518  298557 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:36 CASCA k3s[298557]: time="2025-03-12T16:34:36+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:34:36 CASCA k3s[298557]: time="2025-03-12T16:34:36+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:34:36 CASCA k3s[298557]: W0312 16:34:36.831930  298557 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:36 CASCA k3s[298557]: I0312 16:34:36.832005  298557 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:34:36 CASCA k3s[298557]: time="2025-03-12T16:34:36+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:34:36 CASCA k3s[298557]: time="2025-03-12T16:34:36+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:34:36 CASCA k3s[298557]: time="2025-03-12T16:34:36+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:34:36 CASCA k3s[298557]: time="2025-03-12T16:34:36+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:34:36 CASCA k3s[298557]: time="2025-03-12T16:34:36+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:34:36 CASCA k3s[298557]: I0312 16:34:36.833202  298557 server.go:150] Version: v1.31.6+k3s1
mar 12 16:34:36 CASCA k3s[298557]: I0312 16:34:36.833219  298557 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:34:36 CASCA k3s[298557]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:34:36 CASCA k3s[298557]: time="2025-03-12T16:34:36+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:34:36 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:34:36 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:34:36 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 115749 and the job result is failed.
mar 12 16:34:42 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1203.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:34:42 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 115843 and the job result is done.
mar 12 16:34:42 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 115843.
mar 12 16:34:42 CASCA sh[298893]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:34:42 CASCA k3s[298900]: time="2025-03-12T16:34:42+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:34:42 CASCA k3s[298900]: time="2025-03-12T16:34:42+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:34:42 CASCA k3s[298900]: time="2025-03-12T16:34:42+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:34:42 CASCA k3s[298900]: time="2025-03-12T16:34:42+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:34:42 CASCA k3s[298900]: time="2025-03-12T16:34:42+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:34:42 CASCA k3s[298900]: time="2025-03-12T16:34:42+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:34:42 CASCA k3s[298900]: time="2025-03-12T16:34:42+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:34:42 CASCA k3s[298900]: time="2025-03-12T16:34:42+01:00" 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"
mar 12 16:34:42 CASCA k3s[298900]: W0312 16:34:42.317495  298900 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:42 CASCA k3s[298900]: time="2025-03-12T16:34:42+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:34:42 CASCA k3s[298900]: time="2025-03-12T16:34:42+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:34:42 CASCA k3s[298900]: W0312 16:34:42.317968  298900 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:42 CASCA k3s[298900]: I0312 16:34:42.318096  298900 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:34:42 CASCA k3s[298900]: time="2025-03-12T16:34:42+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:34:42 CASCA k3s[298900]: time="2025-03-12T16:34:42+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:34:42 CASCA k3s[298900]: time="2025-03-12T16:34:42+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:34:42 CASCA k3s[298900]: time="2025-03-12T16:34:42+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:34:42 CASCA k3s[298900]: time="2025-03-12T16:34:42+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:34:42 CASCA k3s[298900]: I0312 16:34:42.319313  298900 server.go:150] Version: v1.31.6+k3s1
mar 12 16:34:42 CASCA k3s[298900]: I0312 16:34:42.319326  298900 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:34:42 CASCA k3s[298900]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:34:42 CASCA k3s[298900]: time="2025-03-12T16:34:42+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:34:42 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:34:42 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:34:42 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 115843 and the job result is failed.
mar 12 16:34:47 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1204.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:34:47 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 115937 and the job result is done.
mar 12 16:34:47 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 115937.
mar 12 16:34:47 CASCA sh[299237]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:34:47 CASCA k3s[299241]: time="2025-03-12T16:34:47+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:34:47 CASCA k3s[299241]: time="2025-03-12T16:34:47+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:34:47 CASCA k3s[299241]: time="2025-03-12T16:34:47+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:34:47 CASCA k3s[299241]: time="2025-03-12T16:34:47+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:34:47 CASCA k3s[299241]: time="2025-03-12T16:34:47+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:34:47 CASCA k3s[299241]: time="2025-03-12T16:34:47+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:34:47 CASCA k3s[299241]: time="2025-03-12T16:34:47+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:34:47 CASCA k3s[299241]: time="2025-03-12T16:34:47+01:00" 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"
mar 12 16:34:47 CASCA k3s[299241]: time="2025-03-12T16:34:47+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:34:47 CASCA k3s[299241]: W0312 16:34:47.794187  299241 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:47 CASCA k3s[299241]: time="2025-03-12T16:34:47+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:34:47 CASCA k3s[299241]: W0312 16:34:47.794640  299241 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:47 CASCA k3s[299241]: I0312 16:34:47.794699  299241 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:34:47 CASCA k3s[299241]: time="2025-03-12T16:34:47+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:34:47 CASCA k3s[299241]: time="2025-03-12T16:34:47+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:34:47 CASCA k3s[299241]: time="2025-03-12T16:34:47+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:34:47 CASCA k3s[299241]: time="2025-03-12T16:34:47+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:34:47 CASCA k3s[299241]: time="2025-03-12T16:34:47+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:34:47 CASCA k3s[299241]: I0312 16:34:47.795958  299241 server.go:150] Version: v1.31.6+k3s1
mar 12 16:34:47 CASCA k3s[299241]: I0312 16:34:47.795975  299241 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:34:47 CASCA k3s[299241]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:34:47 CASCA k3s[299241]: time="2025-03-12T16:34:47+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:34:47 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:34:47 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:34:47 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 115937 and the job result is failed.
mar 12 16:34:53 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1205.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:34:53 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 116031 and the job result is done.
mar 12 16:34:53 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 116031.
mar 12 16:34:53 CASCA sh[299546]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:34:53 CASCA k3s[299553]: time="2025-03-12T16:34:53+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:34:53 CASCA k3s[299553]: time="2025-03-12T16:34:53+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:34:53 CASCA k3s[299553]: time="2025-03-12T16:34:53+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:34:53 CASCA k3s[299553]: time="2025-03-12T16:34:53+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:34:53 CASCA k3s[299553]: time="2025-03-12T16:34:53+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:34:53 CASCA k3s[299553]: time="2025-03-12T16:34:53+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:34:53 CASCA k3s[299553]: time="2025-03-12T16:34:53+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:34:53 CASCA k3s[299553]: time="2025-03-12T16:34:53+01:00" 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"
mar 12 16:34:53 CASCA k3s[299553]: time="2025-03-12T16:34:53+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:34:53 CASCA k3s[299553]: I0312 16:34:53.313071  299553 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:34:53 CASCA k3s[299553]: W0312 16:34:53.313285  299553 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:53 CASCA k3s[299553]: time="2025-03-12T16:34:53+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:34:53 CASCA k3s[299553]: W0312 16:34:53.313674  299553 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:53 CASCA k3s[299553]: time="2025-03-12T16:34:53+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:34:53 CASCA k3s[299553]: time="2025-03-12T16:34:53+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:34:53 CASCA k3s[299553]: I0312 16:34:53.314512  299553 server.go:150] Version: v1.31.6+k3s1
mar 12 16:34:53 CASCA k3s[299553]: I0312 16:34:53.314537  299553 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:34:53 CASCA k3s[299553]: time="2025-03-12T16:34:53+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:34:53 CASCA k3s[299553]: time="2025-03-12T16:34:53+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:34:53 CASCA k3s[299553]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:34:53 CASCA k3s[299553]: time="2025-03-12T16:34:53+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:34:53 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:34:53 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:34:53 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 116031 and the job result is failed.
mar 12 16:34:58 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1206.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:34:58 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 116125 and the job result is done.
mar 12 16:34:58 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 116125.
mar 12 16:34:58 CASCA sh[299943]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:34:58 CASCA k3s[299952]: time="2025-03-12T16:34:58+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:34:58 CASCA k3s[299952]: time="2025-03-12T16:34:58+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:34:58 CASCA k3s[299952]: time="2025-03-12T16:34:58+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:34:58 CASCA k3s[299952]: time="2025-03-12T16:34:58+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:34:58 CASCA k3s[299952]: time="2025-03-12T16:34:58+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:34:58 CASCA k3s[299952]: time="2025-03-12T16:34:58+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:34:58 CASCA k3s[299952]: time="2025-03-12T16:34:58+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:34:58 CASCA k3s[299952]: time="2025-03-12T16:34:58+01:00" 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"
mar 12 16:34:58 CASCA k3s[299952]: W0312 16:34:58.829118  299952 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:58 CASCA k3s[299952]: time="2025-03-12T16:34:58+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:34:58 CASCA k3s[299952]: time="2025-03-12T16:34:58+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:34:58 CASCA k3s[299952]: W0312 16:34:58.829576  299952 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:34:58 CASCA k3s[299952]: I0312 16:34:58.829643  299952 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:34:58 CASCA k3s[299952]: time="2025-03-12T16:34:58+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:34:58 CASCA k3s[299952]: time="2025-03-12T16:34:58+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:34:58 CASCA k3s[299952]: time="2025-03-12T16:34:58+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:34:58 CASCA k3s[299952]: time="2025-03-12T16:34:58+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:34:58 CASCA k3s[299952]: time="2025-03-12T16:34:58+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:34:58 CASCA k3s[299952]: I0312 16:34:58.830859  299952 server.go:150] Version: v1.31.6+k3s1
mar 12 16:34:58 CASCA k3s[299952]: I0312 16:34:58.830875  299952 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:34:58 CASCA k3s[299952]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:34:58 CASCA k3s[299952]: time="2025-03-12T16:34:58+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:34:58 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:34:58 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:34:58 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 116125 and the job result is failed.
mar 12 16:35:04 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1207.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:35:04 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 116219 and the job result is done.
mar 12 16:35:04 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 116219.
mar 12 16:35:04 CASCA sh[300339]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:35:04 CASCA k3s[300346]: time="2025-03-12T16:35:04+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:35:04 CASCA k3s[300346]: time="2025-03-12T16:35:04+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:35:04 CASCA k3s[300346]: time="2025-03-12T16:35:04+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:35:04 CASCA k3s[300346]: time="2025-03-12T16:35:04+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:35:04 CASCA k3s[300346]: time="2025-03-12T16:35:04+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:35:04 CASCA k3s[300346]: time="2025-03-12T16:35:04+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:35:04 CASCA k3s[300346]: time="2025-03-12T16:35:04+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:35:04 CASCA k3s[300346]: time="2025-03-12T16:35:04+01:00" 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"
mar 12 16:35:04 CASCA k3s[300346]: W0312 16:35:04.287210  300346 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:04 CASCA k3s[300346]: time="2025-03-12T16:35:04+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:35:04 CASCA k3s[300346]: time="2025-03-12T16:35:04+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:35:04 CASCA k3s[300346]: W0312 16:35:04.287660  300346 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:04 CASCA k3s[300346]: I0312 16:35:04.287792  300346 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:35:04 CASCA k3s[300346]: time="2025-03-12T16:35:04+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:35:04 CASCA k3s[300346]: time="2025-03-12T16:35:04+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:35:04 CASCA k3s[300346]: time="2025-03-12T16:35:04+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:35:04 CASCA k3s[300346]: time="2025-03-12T16:35:04+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:35:04 CASCA k3s[300346]: time="2025-03-12T16:35:04+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:35:04 CASCA k3s[300346]: I0312 16:35:04.289169  300346 server.go:150] Version: v1.31.6+k3s1
mar 12 16:35:04 CASCA k3s[300346]: I0312 16:35:04.289196  300346 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:35:04 CASCA k3s[300346]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:35:04 CASCA k3s[300346]: time="2025-03-12T16:35:04+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:35:04 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:35:04 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:35:04 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 116219 and the job result is failed.
mar 12 16:35:09 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1208.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:35:09 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 116313 and the job result is done.
mar 12 16:35:09 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 116313.
mar 12 16:35:09 CASCA sh[300731]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:35:09 CASCA k3s[300739]: time="2025-03-12T16:35:09+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:35:09 CASCA k3s[300739]: time="2025-03-12T16:35:09+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:35:09 CASCA k3s[300739]: time="2025-03-12T16:35:09+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:35:09 CASCA k3s[300739]: time="2025-03-12T16:35:09+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:35:09 CASCA k3s[300739]: time="2025-03-12T16:35:09+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:35:09 CASCA k3s[300739]: time="2025-03-12T16:35:09+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:35:09 CASCA k3s[300739]: time="2025-03-12T16:35:09+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:35:09 CASCA k3s[300739]: time="2025-03-12T16:35:09+01:00" 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"
mar 12 16:35:09 CASCA k3s[300739]: W0312 16:35:09.834674  300739 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:09 CASCA k3s[300739]: time="2025-03-12T16:35:09+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:35:09 CASCA k3s[300739]: time="2025-03-12T16:35:09+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:35:09 CASCA k3s[300739]: W0312 16:35:09.835024  300739 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:09 CASCA k3s[300739]: I0312 16:35:09.835170  300739 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:35:09 CASCA k3s[300739]: time="2025-03-12T16:35:09+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:35:09 CASCA k3s[300739]: time="2025-03-12T16:35:09+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:35:09 CASCA k3s[300739]: time="2025-03-12T16:35:09+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:35:09 CASCA k3s[300739]: time="2025-03-12T16:35:09+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:35:09 CASCA k3s[300739]: time="2025-03-12T16:35:09+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:35:09 CASCA k3s[300739]: I0312 16:35:09.836389  300739 server.go:150] Version: v1.31.6+k3s1
mar 12 16:35:09 CASCA k3s[300739]: I0312 16:35:09.836409  300739 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:35:09 CASCA k3s[300739]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:35:09 CASCA k3s[300739]: time="2025-03-12T16:35:09+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:35:09 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:35:09 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:35:09 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 116313 and the job result is failed.
mar 12 16:35:15 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1209.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:35:15 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 116407 and the job result is done.
mar 12 16:35:15 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 116407.
mar 12 16:35:15 CASCA sh[301001]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:35:15 CASCA k3s[301005]: time="2025-03-12T16:35:15+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:35:15 CASCA k3s[301005]: time="2025-03-12T16:35:15+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:35:15 CASCA k3s[301005]: time="2025-03-12T16:35:15+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:35:15 CASCA k3s[301005]: time="2025-03-12T16:35:15+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:35:15 CASCA k3s[301005]: time="2025-03-12T16:35:15+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:35:15 CASCA k3s[301005]: time="2025-03-12T16:35:15+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:35:15 CASCA k3s[301005]: time="2025-03-12T16:35:15+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:35:15 CASCA k3s[301005]: time="2025-03-12T16:35:15+01:00" 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"
mar 12 16:35:15 CASCA k3s[301005]: W0312 16:35:15.277839  301005 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:15 CASCA k3s[301005]: time="2025-03-12T16:35:15+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:35:15 CASCA k3s[301005]: time="2025-03-12T16:35:15+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:35:15 CASCA k3s[301005]: W0312 16:35:15.278187  301005 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:15 CASCA k3s[301005]: I0312 16:35:15.278304  301005 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:35:15 CASCA k3s[301005]: time="2025-03-12T16:35:15+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:35:15 CASCA k3s[301005]: time="2025-03-12T16:35:15+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:35:15 CASCA k3s[301005]: time="2025-03-12T16:35:15+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:35:15 CASCA k3s[301005]: time="2025-03-12T16:35:15+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:35:15 CASCA k3s[301005]: time="2025-03-12T16:35:15+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:35:15 CASCA k3s[301005]: I0312 16:35:15.279488  301005 server.go:150] Version: v1.31.6+k3s1
mar 12 16:35:15 CASCA k3s[301005]: I0312 16:35:15.279552  301005 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:35:15 CASCA k3s[301005]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:35:15 CASCA k3s[301005]: time="2025-03-12T16:35:15+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:35:15 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:35:15 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:35:15 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 116407 and the job result is failed.
mar 12 16:35:20 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1210.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:35:20 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 116501 and the job result is done.
mar 12 16:35:20 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 116501.
mar 12 16:35:20 CASCA sh[301218]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:35:20 CASCA k3s[301225]: time="2025-03-12T16:35:20+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:35:20 CASCA k3s[301225]: time="2025-03-12T16:35:20+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:35:20 CASCA k3s[301225]: time="2025-03-12T16:35:20+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:35:20 CASCA k3s[301225]: time="2025-03-12T16:35:20+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:35:20 CASCA k3s[301225]: time="2025-03-12T16:35:20+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:35:20 CASCA k3s[301225]: time="2025-03-12T16:35:20+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:35:20 CASCA k3s[301225]: time="2025-03-12T16:35:20+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:35:20 CASCA k3s[301225]: time="2025-03-12T16:35:20+01:00" 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"
mar 12 16:35:20 CASCA k3s[301225]: W0312 16:35:20.847052  301225 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:20 CASCA k3s[301225]: time="2025-03-12T16:35:20+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:35:20 CASCA k3s[301225]: time="2025-03-12T16:35:20+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:35:20 CASCA k3s[301225]: W0312 16:35:20.847398  301225 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:20 CASCA k3s[301225]: I0312 16:35:20.847542  301225 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:35:20 CASCA k3s[301225]: time="2025-03-12T16:35:20+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:35:20 CASCA k3s[301225]: time="2025-03-12T16:35:20+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:35:20 CASCA k3s[301225]: time="2025-03-12T16:35:20+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:35:20 CASCA k3s[301225]: time="2025-03-12T16:35:20+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:35:20 CASCA k3s[301225]: time="2025-03-12T16:35:20+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:35:20 CASCA k3s[301225]: I0312 16:35:20.848722  301225 server.go:150] Version: v1.31.6+k3s1
mar 12 16:35:20 CASCA k3s[301225]: I0312 16:35:20.848739  301225 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:35:20 CASCA k3s[301225]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:35:20 CASCA k3s[301225]: time="2025-03-12T16:35:20+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:35:20 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:35:20 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:35:20 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 116501 and the job result is failed.
mar 12 16:35:26 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1211.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:35:26 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 116595 and the job result is done.
mar 12 16:35:26 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 116595.
mar 12 16:35:26 CASCA sh[301551]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:35:26 CASCA k3s[301557]: time="2025-03-12T16:35:26+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:35:26 CASCA k3s[301557]: time="2025-03-12T16:35:26+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:35:26 CASCA k3s[301557]: time="2025-03-12T16:35:26+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:35:26 CASCA k3s[301557]: time="2025-03-12T16:35:26+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:35:26 CASCA k3s[301557]: time="2025-03-12T16:35:26+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:35:26 CASCA k3s[301557]: time="2025-03-12T16:35:26+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:35:26 CASCA k3s[301557]: time="2025-03-12T16:35:26+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:35:26 CASCA k3s[301557]: time="2025-03-12T16:35:26+01:00" 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"
mar 12 16:35:26 CASCA k3s[301557]: W0312 16:35:26.284751  301557 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:26 CASCA k3s[301557]: time="2025-03-12T16:35:26+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:35:26 CASCA k3s[301557]: time="2025-03-12T16:35:26+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:35:26 CASCA k3s[301557]: W0312 16:35:26.285236  301557 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:26 CASCA k3s[301557]: I0312 16:35:26.285265  301557 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:35:26 CASCA k3s[301557]: time="2025-03-12T16:35:26+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:35:26 CASCA k3s[301557]: time="2025-03-12T16:35:26+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:35:26 CASCA k3s[301557]: time="2025-03-12T16:35:26+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:35:26 CASCA k3s[301557]: time="2025-03-12T16:35:26+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:35:26 CASCA k3s[301557]: time="2025-03-12T16:35:26+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:35:26 CASCA k3s[301557]: I0312 16:35:26.286462  301557 server.go:150] Version: v1.31.6+k3s1
mar 12 16:35:26 CASCA k3s[301557]: I0312 16:35:26.286487  301557 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:35:26 CASCA k3s[301557]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:35:26 CASCA k3s[301557]: time="2025-03-12T16:35:26+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:35:26 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:35:26 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:35:26 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 116595 and the job result is failed.
mar 12 16:35:31 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1212.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:35:31 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 116689 and the job result is done.
mar 12 16:35:31 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 116689.
mar 12 16:35:31 CASCA sh[301968]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:35:31 CASCA k3s[301978]: time="2025-03-12T16:35:31+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:35:31 CASCA k3s[301978]: time="2025-03-12T16:35:31+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:35:31 CASCA k3s[301978]: time="2025-03-12T16:35:31+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:35:31 CASCA k3s[301978]: time="2025-03-12T16:35:31+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:35:31 CASCA k3s[301978]: time="2025-03-12T16:35:31+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:35:31 CASCA k3s[301978]: time="2025-03-12T16:35:31+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:35:31 CASCA k3s[301978]: time="2025-03-12T16:35:31+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:35:31 CASCA k3s[301978]: time="2025-03-12T16:35:31+01:00" 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"
mar 12 16:35:31 CASCA k3s[301978]: W0312 16:35:31.804367  301978 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:31 CASCA k3s[301978]: time="2025-03-12T16:35:31+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:35:31 CASCA k3s[301978]: time="2025-03-12T16:35:31+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:35:31 CASCA k3s[301978]: I0312 16:35:31.804877  301978 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:35:31 CASCA k3s[301978]: W0312 16:35:31.804884  301978 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:31 CASCA k3s[301978]: time="2025-03-12T16:35:31+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:35:31 CASCA k3s[301978]: time="2025-03-12T16:35:31+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:35:31 CASCA k3s[301978]: time="2025-03-12T16:35:31+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:35:31 CASCA k3s[301978]: time="2025-03-12T16:35:31+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:35:31 CASCA k3s[301978]: time="2025-03-12T16:35:31+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:35:31 CASCA k3s[301978]: I0312 16:35:31.806067  301978 server.go:150] Version: v1.31.6+k3s1
mar 12 16:35:31 CASCA k3s[301978]: I0312 16:35:31.806086  301978 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:35:31 CASCA k3s[301978]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:35:31 CASCA k3s[301978]: time="2025-03-12T16:35:31+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:35:31 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:35:31 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:35:31 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 116689 and the job result is failed.
mar 12 16:35:37 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1213.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:35:37 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 116783 and the job result is done.
mar 12 16:35:37 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 116783.
mar 12 16:35:37 CASCA sh[302412]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:35:37 CASCA k3s[302419]: time="2025-03-12T16:35:37+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:35:37 CASCA k3s[302419]: time="2025-03-12T16:35:37+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:35:37 CASCA k3s[302419]: time="2025-03-12T16:35:37+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:35:37 CASCA k3s[302419]: time="2025-03-12T16:35:37+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:35:37 CASCA k3s[302419]: time="2025-03-12T16:35:37+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:35:37 CASCA k3s[302419]: time="2025-03-12T16:35:37+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:35:37 CASCA k3s[302419]: time="2025-03-12T16:35:37+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:35:37 CASCA k3s[302419]: time="2025-03-12T16:35:37+01:00" 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"
mar 12 16:35:37 CASCA k3s[302419]: W0312 16:35:37.306964  302419 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:37 CASCA k3s[302419]: time="2025-03-12T16:35:37+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:35:37 CASCA k3s[302419]: time="2025-03-12T16:35:37+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:35:37 CASCA k3s[302419]: W0312 16:35:37.307299  302419 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:37 CASCA k3s[302419]: I0312 16:35:37.307457  302419 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:35:37 CASCA k3s[302419]: time="2025-03-12T16:35:37+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:35:37 CASCA k3s[302419]: time="2025-03-12T16:35:37+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:35:37 CASCA k3s[302419]: time="2025-03-12T16:35:37+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:35:37 CASCA k3s[302419]: time="2025-03-12T16:35:37+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:35:37 CASCA k3s[302419]: time="2025-03-12T16:35:37+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:35:37 CASCA k3s[302419]: I0312 16:35:37.308674  302419 server.go:150] Version: v1.31.6+k3s1
mar 12 16:35:37 CASCA k3s[302419]: I0312 16:35:37.308687  302419 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:35:37 CASCA k3s[302419]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:35:37 CASCA k3s[302419]: time="2025-03-12T16:35:37+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:35:37 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:35:37 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:35:37 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 116783 and the job result is failed.
mar 12 16:35:42 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1214.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:35:42 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 116877 and the job result is done.
mar 12 16:35:42 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 116877.
mar 12 16:35:42 CASCA sh[302739]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:35:42 CASCA k3s[302746]: time="2025-03-12T16:35:42+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:35:42 CASCA k3s[302746]: time="2025-03-12T16:35:42+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:35:42 CASCA k3s[302746]: time="2025-03-12T16:35:42+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:35:42 CASCA k3s[302746]: time="2025-03-12T16:35:42+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:35:42 CASCA k3s[302746]: time="2025-03-12T16:35:42+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:35:42 CASCA k3s[302746]: time="2025-03-12T16:35:42+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:35:42 CASCA k3s[302746]: time="2025-03-12T16:35:42+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:35:42 CASCA k3s[302746]: time="2025-03-12T16:35:42+01:00" 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"
mar 12 16:35:42 CASCA k3s[302746]: W0312 16:35:42.787970  302746 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:42 CASCA k3s[302746]: time="2025-03-12T16:35:42+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:35:42 CASCA k3s[302746]: time="2025-03-12T16:35:42+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:35:42 CASCA k3s[302746]: W0312 16:35:42.788435  302746 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:42 CASCA k3s[302746]: I0312 16:35:42.788552  302746 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:35:42 CASCA k3s[302746]: time="2025-03-12T16:35:42+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:35:42 CASCA k3s[302746]: time="2025-03-12T16:35:42+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:35:42 CASCA k3s[302746]: time="2025-03-12T16:35:42+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:35:42 CASCA k3s[302746]: time="2025-03-12T16:35:42+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:35:42 CASCA k3s[302746]: time="2025-03-12T16:35:42+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:35:42 CASCA k3s[302746]: I0312 16:35:42.789773  302746 server.go:150] Version: v1.31.6+k3s1
mar 12 16:35:42 CASCA k3s[302746]: I0312 16:35:42.789788  302746 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:35:42 CASCA k3s[302746]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:35:42 CASCA k3s[302746]: time="2025-03-12T16:35:42+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:35:42 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:35:42 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:35:42 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 116877 and the job result is failed.
mar 12 16:35:48 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1215.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:35:48 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 116971 and the job result is done.
mar 12 16:35:48 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 116971.
mar 12 16:35:48 CASCA sh[302919]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:35:48 CASCA k3s[302925]: time="2025-03-12T16:35:48+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:35:48 CASCA k3s[302925]: time="2025-03-12T16:35:48+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:35:48 CASCA k3s[302925]: time="2025-03-12T16:35:48+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:35:48 CASCA k3s[302925]: time="2025-03-12T16:35:48+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:35:48 CASCA k3s[302925]: time="2025-03-12T16:35:48+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:35:48 CASCA k3s[302925]: time="2025-03-12T16:35:48+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:35:48 CASCA k3s[302925]: time="2025-03-12T16:35:48+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:35:48 CASCA k3s[302925]: time="2025-03-12T16:35:48+01:00" 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"
mar 12 16:35:48 CASCA k3s[302925]: W0312 16:35:48.329161  302925 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:48 CASCA k3s[302925]: time="2025-03-12T16:35:48+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:35:48 CASCA k3s[302925]: time="2025-03-12T16:35:48+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:35:48 CASCA k3s[302925]: W0312 16:35:48.329565  302925 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:48 CASCA k3s[302925]: I0312 16:35:48.329702  302925 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:35:48 CASCA k3s[302925]: time="2025-03-12T16:35:48+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:35:48 CASCA k3s[302925]: time="2025-03-12T16:35:48+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:35:48 CASCA k3s[302925]: time="2025-03-12T16:35:48+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:35:48 CASCA k3s[302925]: time="2025-03-12T16:35:48+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:35:48 CASCA k3s[302925]: time="2025-03-12T16:35:48+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:35:48 CASCA k3s[302925]: I0312 16:35:48.330938  302925 server.go:150] Version: v1.31.6+k3s1
mar 12 16:35:48 CASCA k3s[302925]: I0312 16:35:48.330953  302925 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:35:48 CASCA k3s[302925]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:35:48 CASCA k3s[302925]: time="2025-03-12T16:35:48+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:35:48 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:35:48 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:35:48 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 116971 and the job result is failed.
mar 12 16:35:53 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1216.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:35:53 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 117065 and the job result is done.
mar 12 16:35:53 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 117065.
mar 12 16:35:53 CASCA sh[303334]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:35:53 CASCA k3s[303341]: time="2025-03-12T16:35:53+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:35:53 CASCA k3s[303341]: time="2025-03-12T16:35:53+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:35:53 CASCA k3s[303341]: time="2025-03-12T16:35:53+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:35:53 CASCA k3s[303341]: time="2025-03-12T16:35:53+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:35:53 CASCA k3s[303341]: time="2025-03-12T16:35:53+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:35:53 CASCA k3s[303341]: time="2025-03-12T16:35:53+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:35:53 CASCA k3s[303341]: time="2025-03-12T16:35:53+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:35:53 CASCA k3s[303341]: time="2025-03-12T16:35:53+01:00" 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"
mar 12 16:35:53 CASCA k3s[303341]: W0312 16:35:53.775748  303341 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:53 CASCA k3s[303341]: time="2025-03-12T16:35:53+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:35:53 CASCA k3s[303341]: time="2025-03-12T16:35:53+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:35:53 CASCA k3s[303341]: W0312 16:35:53.776216  303341 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:53 CASCA k3s[303341]: I0312 16:35:53.776414  303341 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:35:53 CASCA k3s[303341]: time="2025-03-12T16:35:53+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:35:53 CASCA k3s[303341]: time="2025-03-12T16:35:53+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:35:53 CASCA k3s[303341]: time="2025-03-12T16:35:53+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:35:53 CASCA k3s[303341]: time="2025-03-12T16:35:53+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:35:53 CASCA k3s[303341]: time="2025-03-12T16:35:53+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:35:53 CASCA k3s[303341]: I0312 16:35:53.777956  303341 server.go:150] Version: v1.31.6+k3s1
mar 12 16:35:53 CASCA k3s[303341]: I0312 16:35:53.777983  303341 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:35:53 CASCA k3s[303341]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:35:53 CASCA k3s[303341]: time="2025-03-12T16:35:53+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:35:53 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:35:53 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:35:53 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 117065 and the job result is failed.
mar 12 16:35:59 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1217.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:35:59 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 117159 and the job result is done.
mar 12 16:35:59 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 117159.
mar 12 16:35:59 CASCA sh[303731]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:35:59 CASCA k3s[303740]: time="2025-03-12T16:35:59+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:35:59 CASCA k3s[303740]: time="2025-03-12T16:35:59+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:35:59 CASCA k3s[303740]: time="2025-03-12T16:35:59+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:35:59 CASCA k3s[303740]: time="2025-03-12T16:35:59+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:35:59 CASCA k3s[303740]: time="2025-03-12T16:35:59+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:35:59 CASCA k3s[303740]: time="2025-03-12T16:35:59+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:35:59 CASCA k3s[303740]: time="2025-03-12T16:35:59+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:35:59 CASCA k3s[303740]: time="2025-03-12T16:35:59+01:00" 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"
mar 12 16:35:59 CASCA k3s[303740]: W0312 16:35:59.333474  303740 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:59 CASCA k3s[303740]: time="2025-03-12T16:35:59+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:35:59 CASCA k3s[303740]: time="2025-03-12T16:35:59+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:35:59 CASCA k3s[303740]: W0312 16:35:59.333847  303740 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:35:59 CASCA k3s[303740]: time="2025-03-12T16:35:59+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:35:59 CASCA k3s[303740]: time="2025-03-12T16:35:59+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:35:59 CASCA k3s[303740]: time="2025-03-12T16:35:59+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:35:59 CASCA k3s[303740]: time="2025-03-12T16:35:59+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:35:59 CASCA k3s[303740]: I0312 16:35:59.334728  303740 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:35:59 CASCA k3s[303740]: time="2025-03-12T16:35:59+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:35:59 CASCA k3s[303740]: time="2025-03-12T16:35:59+01:00" level=info msg="Wrote kubeconfig /etc/rancher/k3s/k3s.yaml"
mar 12 16:35:59 CASCA k3s[303740]: time="2025-03-12T16:35:59+01:00" level=info msg="Run: k3s kubectl"
mar 12 16:35:59 CASCA k3s[303740]: I0312 16:35:59.335953  303740 server.go:150] Version: v1.31.6+k3s1
mar 12 16:35:59 CASCA k3s[303740]: I0312 16:35:59.335979  303740 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:35:59 CASCA k3s[303740]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:35:59 CASCA k3s[303740]: time="2025-03-12T16:35:59+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:35:59 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:35:59 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:35:59 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 117159 and the job result is failed.
mar 12 16:36:04 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1218.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:36:04 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 117253 and the job result is done.
mar 12 16:36:04 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 117253.
mar 12 16:36:04 CASCA sh[304097]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:36:04 CASCA k3s[304102]: time="2025-03-12T16:36:04+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:36:04 CASCA k3s[304102]: time="2025-03-12T16:36:04+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:36:04 CASCA k3s[304102]: time="2025-03-12T16:36:04+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:36:04 CASCA k3s[304102]: time="2025-03-12T16:36:04+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:36:04 CASCA k3s[304102]: time="2025-03-12T16:36:04+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:36:04 CASCA k3s[304102]: time="2025-03-12T16:36:04+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:36:04 CASCA k3s[304102]: time="2025-03-12T16:36:04+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:36:04 CASCA k3s[304102]: time="2025-03-12T16:36:04+01:00" 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"
mar 12 16:36:04 CASCA k3s[304102]: time="2025-03-12T16:36:04+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:36:04 CASCA k3s[304102]: W0312 16:36:04.793723  304102 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:36:04 CASCA k3s[304102]: time="2025-03-12T16:36:04+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:36:04 CASCA k3s[304102]: W0312 16:36:04.794088  304102 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:36:04 CASCA k3s[304102]: I0312 16:36:04.794164  304102 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:36:04 CASCA k3s[304102]: time="2025-03-12T16:36:04+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:36:04 CASCA k3s[304102]: time="2025-03-12T16:36:04+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:36:04 CASCA k3s[304102]: time="2025-03-12T16:36:04+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:36:04 CASCA k3s[304102]: time="2025-03-12T16:36:04+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:36:04 CASCA k3s[304102]: time="2025-03-12T16:36:04+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:36:04 CASCA k3s[304102]: I0312 16:36:04.795363  304102 server.go:150] Version: v1.31.6+k3s1
mar 12 16:36:04 CASCA k3s[304102]: I0312 16:36:04.795376  304102 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:36:04 CASCA k3s[304102]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:36:04 CASCA k3s[304102]: time="2025-03-12T16:36:04+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:36:04 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:36:04 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:36:04 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 117253 and the job result is failed.
mar 12 16:36:10 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1219.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:36:10 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 117347 and the job result is done.
mar 12 16:36:10 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 117347.
mar 12 16:36:10 CASCA sh[304421]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:36:10 CASCA k3s[304427]: time="2025-03-12T16:36:10+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:36:10 CASCA k3s[304427]: time="2025-03-12T16:36:10+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:36:10 CASCA k3s[304427]: time="2025-03-12T16:36:10+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:36:10 CASCA k3s[304427]: time="2025-03-12T16:36:10+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:36:10 CASCA k3s[304427]: time="2025-03-12T16:36:10+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:36:10 CASCA k3s[304427]: time="2025-03-12T16:36:10+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:36:10 CASCA k3s[304427]: time="2025-03-12T16:36:10+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:36:10 CASCA k3s[304427]: time="2025-03-12T16:36:10+01:00" 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"
mar 12 16:36:10 CASCA k3s[304427]: W0312 16:36:10.320641  304427 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:36:10 CASCA k3s[304427]: time="2025-03-12T16:36:10+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:36:10 CASCA k3s[304427]: time="2025-03-12T16:36:10+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:36:10 CASCA k3s[304427]: W0312 16:36:10.321156  304427 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:36:10 CASCA k3s[304427]: I0312 16:36:10.321301  304427 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:36:10 CASCA k3s[304427]: time="2025-03-12T16:36:10+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:36:10 CASCA k3s[304427]: time="2025-03-12T16:36:10+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:36:10 CASCA k3s[304427]: time="2025-03-12T16:36:10+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:36:10 CASCA k3s[304427]: time="2025-03-12T16:36:10+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:36:10 CASCA k3s[304427]: time="2025-03-12T16:36:10+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:36:10 CASCA k3s[304427]: I0312 16:36:10.322525  304427 server.go:150] Version: v1.31.6+k3s1
mar 12 16:36:10 CASCA k3s[304427]: I0312 16:36:10.322551  304427 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:36:10 CASCA k3s[304427]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:36:10 CASCA k3s[304427]: time="2025-03-12T16:36:10+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:36:10 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:36:10 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:36:10 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 117347 and the job result is failed.
mar 12 16:36:15 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1220.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:36:15 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 117441 and the job result is done.
mar 12 16:36:15 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 117441.
mar 12 16:36:15 CASCA sh[304761]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:36:15 CASCA k3s[304768]: time="2025-03-12T16:36:15+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:36:15 CASCA k3s[304768]: time="2025-03-12T16:36:15+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:36:15 CASCA k3s[304768]: time="2025-03-12T16:36:15+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:36:15 CASCA k3s[304768]: time="2025-03-12T16:36:15+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:36:15 CASCA k3s[304768]: time="2025-03-12T16:36:15+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:36:15 CASCA k3s[304768]: time="2025-03-12T16:36:15+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:36:15 CASCA k3s[304768]: time="2025-03-12T16:36:15+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:36:15 CASCA k3s[304768]: time="2025-03-12T16:36:15+01:00" 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"
mar 12 16:36:15 CASCA k3s[304768]: W0312 16:36:15.830300  304768 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:36:15 CASCA k3s[304768]: time="2025-03-12T16:36:15+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:36:15 CASCA k3s[304768]: time="2025-03-12T16:36:15+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:36:15 CASCA k3s[304768]: W0312 16:36:15.830666  304768 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:36:15 CASCA k3s[304768]: I0312 16:36:15.830819  304768 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:36:15 CASCA k3s[304768]: time="2025-03-12T16:36:15+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:36:15 CASCA k3s[304768]: time="2025-03-12T16:36:15+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:36:15 CASCA k3s[304768]: time="2025-03-12T16:36:15+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:36:15 CASCA k3s[304768]: time="2025-03-12T16:36:15+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:36:15 CASCA k3s[304768]: time="2025-03-12T16:36:15+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:36:15 CASCA k3s[304768]: I0312 16:36:15.832085  304768 server.go:150] Version: v1.31.6+k3s1
mar 12 16:36:15 CASCA k3s[304768]: I0312 16:36:15.832098  304768 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:36:15 CASCA k3s[304768]: time="2025-03-12T16:36:15+01:00" level=info msg="Wrote kubeconfig /etc/rancher/k3s/k3s.yaml"
mar 12 16:36:15 CASCA k3s[304768]: time="2025-03-12T16:36:15+01:00" level=info msg="Run: k3s kubectl"
mar 12 16:36:15 CASCA k3s[304768]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:36:15 CASCA k3s[304768]: time="2025-03-12T16:36:15+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:36:15 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:36:15 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:36:15 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 117441 and the job result is failed.
mar 12 16:36:21 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1221.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:36:21 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 117535 and the job result is done.
mar 12 16:36:21 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 117535.
mar 12 16:36:21 CASCA sh[305102]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:36:21 CASCA k3s[305109]: time="2025-03-12T16:36:21+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:36:21 CASCA k3s[305109]: time="2025-03-12T16:36:21+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:36:21 CASCA k3s[305109]: time="2025-03-12T16:36:21+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:36:21 CASCA k3s[305109]: time="2025-03-12T16:36:21+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:36:21 CASCA k3s[305109]: time="2025-03-12T16:36:21+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:36:21 CASCA k3s[305109]: time="2025-03-12T16:36:21+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:36:21 CASCA k3s[305109]: time="2025-03-12T16:36:21+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:36:21 CASCA k3s[305109]: time="2025-03-12T16:36:21+01:00" 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"
mar 12 16:36:21 CASCA k3s[305109]: time="2025-03-12T16:36:21+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:36:21 CASCA k3s[305109]: W0312 16:36:21.311329  305109 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:36:21 CASCA k3s[305109]: time="2025-03-12T16:36:21+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:36:21 CASCA k3s[305109]: W0312 16:36:21.311673  305109 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:36:21 CASCA k3s[305109]: time="2025-03-12T16:36:21+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:36:21 CASCA k3s[305109]: I0312 16:36:21.311866  305109 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:36:21 CASCA k3s[305109]: time="2025-03-12T16:36:21+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:36:21 CASCA k3s[305109]: time="2025-03-12T16:36:21+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:36:21 CASCA k3s[305109]: time="2025-03-12T16:36:21+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:36:21 CASCA k3s[305109]: time="2025-03-12T16:36:21+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:36:21 CASCA k3s[305109]: I0312 16:36:21.313086  305109 server.go:150] Version: v1.31.6+k3s1
mar 12 16:36:21 CASCA k3s[305109]: I0312 16:36:21.313105  305109 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:36:21 CASCA k3s[305109]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:36:21 CASCA k3s[305109]: time="2025-03-12T16:36:21+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:36:21 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:36:21 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:36:21 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 117535 and the job result is failed.
mar 12 16:36:26 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1222.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:36:26 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 117629 and the job result is done.
mar 12 16:36:26 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 117629.
mar 12 16:36:26 CASCA sh[305425]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:36:26 CASCA k3s[305432]: time="2025-03-12T16:36:26+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:36:26 CASCA k3s[305432]: time="2025-03-12T16:36:26+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:36:26 CASCA k3s[305432]: time="2025-03-12T16:36:26+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:36:26 CASCA k3s[305432]: time="2025-03-12T16:36:26+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:36:26 CASCA k3s[305432]: time="2025-03-12T16:36:26+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:36:26 CASCA k3s[305432]: time="2025-03-12T16:36:26+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:36:26 CASCA k3s[305432]: time="2025-03-12T16:36:26+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:36:26 CASCA k3s[305432]: time="2025-03-12T16:36:26+01:00" 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"
mar 12 16:36:26 CASCA k3s[305432]: W0312 16:36:26.788551  305432 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:36:26 CASCA k3s[305432]: time="2025-03-12T16:36:26+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:36:26 CASCA k3s[305432]: time="2025-03-12T16:36:26+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:36:26 CASCA k3s[305432]: W0312 16:36:26.789039  305432 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:36:26 CASCA k3s[305432]: I0312 16:36:26.789065  305432 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:36:26 CASCA k3s[305432]: time="2025-03-12T16:36:26+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:36:26 CASCA k3s[305432]: time="2025-03-12T16:36:26+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:36:26 CASCA k3s[305432]: time="2025-03-12T16:36:26+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:36:26 CASCA k3s[305432]: time="2025-03-12T16:36:26+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:36:26 CASCA k3s[305432]: time="2025-03-12T16:36:26+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:36:26 CASCA k3s[305432]: I0312 16:36:26.790249  305432 server.go:150] Version: v1.31.6+k3s1
mar 12 16:36:26 CASCA k3s[305432]: I0312 16:36:26.790268  305432 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:36:26 CASCA k3s[305432]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:36:26 CASCA k3s[305432]: time="2025-03-12T16:36:26+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:36:26 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:36:26 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:36:26 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 117629 and the job result is failed.
mar 12 16:36:32 CASCA systemd[1]: k3s.service: Scheduled restart job, restart counter is at 1223.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ Automatic restarting of the unit k3s.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
mar 12 16:36:32 CASCA systemd[1]: Stopped k3s.service - Lightweight Kubernetes.
░░ Subject: A stop job for unit k3s.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A stop job for unit k3s.service has finished.
░░ 
░░ The job identifier is 117723 and the job result is done.
mar 12 16:36:32 CASCA systemd[1]: Starting k3s.service - Lightweight Kubernetes...
░░ Subject: A start job for unit k3s.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has begun execution.
░░ 
░░ The job identifier is 117723.
mar 12 16:36:32 CASCA sh[305771]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
mar 12 16:36:32 CASCA k3s[305779]: time="2025-03-12T16:36:32+01:00" level=info msg="Starting k3s v1.31.6+k3s1 (6ab750f9)"
mar 12 16:36:32 CASCA k3s[305779]: time="2025-03-12T16:36:32+01:00" level=info msg="Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s"
mar 12 16:36:32 CASCA k3s[305779]: time="2025-03-12T16:36:32+01:00" level=info msg="Configuring database table schema and indexes, this may take a moment..."
mar 12 16:36:32 CASCA k3s[305779]: time="2025-03-12T16:36:32+01:00" level=info msg="Database tables and indexes are up to date"
mar 12 16:36:32 CASCA k3s[305779]: time="2025-03-12T16:36:32+01:00" level=info msg="Kine available at unix://kine.sock"
mar 12 16:36:32 CASCA k3s[305779]: time="2025-03-12T16:36:32+01:00" level=info msg="Reconciling bootstrap data between datastore and disk"
mar 12 16:36:32 CASCA k3s[305779]: time="2025-03-12T16:36:32+01:00" 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 --egress-selector-config-file=/var/lib/rancher/k3s/server/etc/egress-selector-config.yaml --enable-admission-plugins=NodeRestriction --enable-aggregator-routing=true --enable-bootstrap-token-auth=true --etcd-servers=unix://kine.sock --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 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --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.current.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-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305 --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
mar 12 16:36:32 CASCA k3s[305779]: time="2025-03-12T16:36:32+01:00" 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"
mar 12 16:36:32 CASCA k3s[305779]: time="2025-03-12T16:36:32+01:00" level=info msg="Waiting for API server to become available"
mar 12 16:36:32 CASCA k3s[305779]: W0312 16:36:32.314610  305779 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:36:32 CASCA k3s[305779]: time="2025-03-12T16:36:32+01:00" 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.nochain.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.nochain.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.nochain.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/server-ca.nochain.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --configure-cloud-routes=false --controllers=*,tokencleaner,-service,-route,-cloud-node-lifecycle --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.current.key --service-cluster-ip-range=10.43.0.0/16 --use-service-account-credentials=true"
mar 12 16:36:32 CASCA k3s[305779]: W0312 16:36:32.315034  305779 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
mar 12 16:36:32 CASCA k3s[305779]: I0312 16:36:32.315101  305779 options.go:228] external host was not specified, using 192.168.1.133
mar 12 16:36:32 CASCA k3s[305779]: time="2025-03-12T16:36:32+01:00" 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-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false"
mar 12 16:36:32 CASCA k3s[305779]: time="2025-03-12T16:36:32+01:00" level=info msg="Server node token is available at /var/lib/rancher/k3s/server/token"
mar 12 16:36:32 CASCA k3s[305779]: time="2025-03-12T16:36:32+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.133:6443 -t ${SERVER_NODE_TOKEN}"
mar 12 16:36:32 CASCA k3s[305779]: time="2025-03-12T16:36:32+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token"
mar 12 16:36:32 CASCA k3s[305779]: time="2025-03-12T16:36:32+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.133:6443 -t ${AGENT_NODE_TOKEN}"
mar 12 16:36:32 CASCA k3s[305779]: I0312 16:36:32.316330  305779 server.go:150] Version: v1.31.6+k3s1
mar 12 16:36:32 CASCA k3s[305779]: I0312 16:36:32.316345  305779 server.go:152] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
mar 12 16:36:32 CASCA k3s[305779]: Error: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use
mar 12 16:36:32 CASCA k3s[305779]: time="2025-03-12T16:36:32+01:00" level=error msg="apiserver exited: failed to create listener: failed to listen on 127.0.0.1:6444: listen tcp 127.0.0.1:6444: bind: address already in use"
mar 12 16:36:32 CASCA systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit k3s.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
mar 12 16:36:32 CASCA systemd[1]: k3s.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit k3s.service has entered the 'failed' state with result 'exit-code'.
mar 12 16:36:32 CASCA systemd[1]: Failed to start k3s.service - Lightweight Kubernetes.
░░ Subject: A start job for unit k3s.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit k3s.service has finished with a failure.
░░ 
░░ The job identifier is 117723 and the job result is failed.