– Unit k3s.service has finished shutting down.
Jun 29 15:17:11 rancher01 systemd[1]: Starting Lightweight Kubernetes…
– Subject: Unit k3s.service has begun start-up
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
– Unit k3s.service has begun starting up.
Jun 29 15:17:11 rancher01 sh[6548]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
Jun 29 15:17:11 rancher01 sh[6548]: Failed to get unit file state for nm-cloud-setup.service: No such file or directory
Jun 29 15:17:11 rancher01 k3s[6555]: time=“2022-06-29T15:17:11.953914618+08:00” level=info msg=“Starting k3s v1.19.16+k3s1 (da168695)”
Jun 29 15:17:11 rancher01 k3s[6555]: time=“2022-06-29T15:17:11.958307626+08:00” level=info msg="Configuring mysql database connection p
Jun 29 15:17:11 rancher01 k3s[6555]: time=“2022-06-29T15:17:11.958370446+08:00” level=info msg="Configuring database table schema and i
Jun 29 15:17:11 rancher01 k3s[6555]: time=“2022-06-29T15:17:11.960750302+08:00” level=fatal msg="starting kubernetes: preparing server:
Jun 29 15:17:11 rancher01 systemd[1]: k3s.service: main process exited, code=exited, status=1/FAILURE
Jun 29 15:17:11 rancher01 systemd[1]: Failed to start Lightweight Kubernetes.
– Subject: Unit k3s.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
– Unit k3s.service has failed.
– The result is failed.
Jun 29 15:17:11 rancher01 systemd[1]: Unit k3s.service entered failed state.
Jun 29 15:17:11 rancher01 systemd[1]: k3s.service failed.