This message was deleted.
# general
a
This message was deleted.
b
What are the logs before "k3s exited with: exit status 1"?
😀 1
c
2023/12/12 132805 [INFO] Rancher version v2.8.0 (72f58378b) is starting 2023/12/12 132805 [INFO] Listening on /tmp/log.sock 2023/12/12 132805 [INFO] Rancher arguments {ACMEDomains:[] AddLocal:true Embedded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:false Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit.log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Features: ClusterRegistry:} 2023/12/12 132805 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.16444 connect: connection refused 2023/12/12 132807 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.16444 connect: connection refused 2023/12/12 132809 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.16444 connect: connection refused 2023/12/12 132811 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.16444 connect: connection refused 2023/12/12 132813 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.16444 connect: connection refused 2023/12/12 132815 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.16444 connect: connection refused 2023/12/12 132817 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.16444 connect: connection refused 2023/12/12 132819 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.16444 connect: connection refused 2023/12/12 132821 [INFO] Running in single server mode, will not peer connections 2023/12/12 132821 [INFO] Applying CRD features.management.cattle.io 2023/12/12 132821 [INFO] Updating embedded CRD clusterroletemplatebindings.management.cattle.io 2023/12/12 132821 [INFO] Updating embedded CRD globalroles.management.cattle.io 2023/12/12 132821 [INFO] Updating embedded CRD globalrolebindings.management.cattle.io 2023/12/12 132821 [INFO] Updating embedded CRD projects.management.cattle.io 2023/12/12 132821 [INFO] Updating embedded CRD projectroletemplatebindings.management.cattle.io 2023/12/12 132821 [INFO] Updating embedded CRD roletemplates.management.cattle.io 2023/12/12 132821 [INFO] Waiting for CRD roletemplates.management.cattle.io to become available 2023/12/12 132827 [FATAL] k3s exited with: exit status 1 INFO: Running k3s server --cluster-init --cluster-reset 2023/12/12 132846 [INFO] Rancher version v2.8.0 (72f58378b) is starting 2023/12/12 132846 [INFO] Rancher arguments {ACMEDomains:[] AddLocal:true Embedded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:false Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit.log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Features: ClusterRegistry:} 2023/12/12 132846 [INFO] Listening on /tmp/log.sock 2023/12/12 132846 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.16444 connect: connection refused 2023/12/12 132848 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.16444 connect: connection refused 2023/12/12 132850 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.16444 connect: connection refused 2023/12/12 132852 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.16444 connect: connection refused 2023/12/12 132854 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6444/version?timeout=15m0s": dial tcp 127.0.0.16444 connect: connection refused
s
turn off machine's firewall or make sure port 6444 is available for TCP connections.
😀 1
c
I have turned off the firewall on the machine, but it does not change.
b
Perhaps you're running into an issue with your cgroups for docker. There's this issue that's related and the documentation of k3s in docker references:
Cgroup v1 and Hybrid v1/v2 are not supported; only pure Cgroup v2 is supported
https://docs.k3s.io/advanced#running-rootless-servers-experimental
👆 2
🥰 1
c
Thanks for the great information. Is editing the /etc/default/grub file the best solution?
b
That really depends on your situation. You should probably backup your grub config before doing anything for peace of mind, but it could at least narrow down what the real issue is.