This message was deleted.
# k3sa
adamant-kite-43734
09/02/2022, 2:10 AMThis message was deleted.
c
creamy-pencil-82913
09/02/2022, 2:33 AMShould be pretty much immediate if it's working. Make sure you have the right server address and that the correct ports are open.
c
chilly-telephone-51989
09/02/2022, 2:34 AMthe machines are ubuntu latest
added firewall rule to enable 6443, later disabled the firewall after 1st failure.
for agents , i first used the localIP of the server and then the external IP. nothing works. it is just stuck
chilly-telephone-51989
09/02/2022, 2:35 AM Copy code
[INFO] systemd: Enabling k3s-agent unit
Created symlink /etc/systemd/system/multi-user.target.wants/k3s-agent.service → /etc/systemd/system/k3s-agent.service.
[INFO] systemd: Starting k3s-agentk
kind-nightfall-56861
09/02/2022, 8:26 AMalso check what health state the pods are in on your master node
c
creamy-pencil-82913
09/02/2022, 8:38 AMwhat do the actual logs say?
creamy-pencil-82913
09/02/2022, 8:38 AMhave you looked at the journald logs on the agents at all?
7 Views