search

techno-tim / k3s-ansible

The easiest way to bootstrap a self-hosted High Availability Kubernetes cluster. A fully automated HA k3s etcd install with kube-vip, MetalLB, and more. Build. Destroy. Repeat.
https://technotim.live/posts/k3s-etcd-ansible/
Apache License 2.0
2.41k stars 1.05k forks source link

Getting k3s.node.service and bind address error after running the playbook #282

Closed GHMCr closed 1 year ago

GHMCr commented 1 year ago

After running the playbook for 3 nucs with ubuntu server on them, everything seems to install and setup fine. But in the last steps I'm getting the following error for all 3 nodes (that are both master and node):

fatal: [node001.calmus.one]: FAILED! => changed=false 
  msg: |-
    Unable to start service k3s-node: Job for k3s-node.service failed because the control process exited with error code.
    See "systemctl status k3s-node.service" and "journalctl -xeu k3s-node.service" for details.

When running the journalctl command on the nodes I find:

Error starting load balancer: listen tcp 127.0.0.1:6444: bind: address already in use

I don't know how to fix this.

timothystewart6 commented 1 year ago

Hi @GHMCr can you please fill out the template when opening an issue rather than deleting it?

timothystewart6 commented 1 year ago

I am going to close this but feel free to open another issue and use the template