Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
c
chilly-telephone-51989
09/02/2022, 2:10 AMi ran the installation for nodes, using the token. how long does it take to start nodes and join cluster. it seems to be taking forever. stuck at
systemd: Starting K3s-agent
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
[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?
have you looked at the journald logs on the agents at all?