magnificent-vr-88571
09/13/2022, 9:05 PMSep 13 17:41:21 svmaster rke2[14824]: time="2022-09-13T17:41:21+09:00" level=info msg="Latest etcd manifest deployed"
Sep 13 17:41:22 svmaster rke2[14824]: {"level":"warn","ts":"2022-09-13T17:41:22.837+0900","caller":"grpclog/grpclog.go:60","msg":"grpc: addrConn.createTransport failed to connect to {<https://127.0.0.1:2379> <nil> 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing dial tcp 127.0.0.1:2379: connect: connection refused\". Reconnecting..."}
Sep 13 17:43:23 svmaster rke2[21854]: time="2022-09-13T17:43:23+09:00" level=info msg="Stopped tunnel to 127.0.0.1:9345"
Sep 13 17:43:23 svmaster rke2[21854]: time="2022-09-13T17:43:23+09:00" level=info msg="Proxy done" err="context canceled" url="<wss://127.0.0.1:9345/v1-rke2/connect>"
Sep 13 17:43:23 svmaster rke2[21854]: time="2022-09-13T17:43:23+09:00" level=info msg="Connecting to proxy" url="<wss://192.168.7.15:9345/v1-rke2/connect>"
Sep 13 17:43:23 svmaster rke2[21854]: time="2022-09-13T17:43:23+09:00" level=info msg="error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF"
Sep 13 17:43:23 svmaster rke2[21854]: time="2022-09-13T17:43:23+09:00" level=info msg="Handling backend connection request [svmaster]"
And in agent journalctl logs following are displayed.
Sep 13 18:03:02 svagent rke2[2659960]: W0913 18:03:02.914417 2659960 clientconn.go:1223] grpc: addrConn.createTransport failed to connect to {<https://127.0.0.1:2379> <nil> 0 <nil>}. Err :connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:2379: connect: connection refused". Reconnecting...
Sep 13 18:03:06 svagent rke2[2659960]: time="2022-09-13T18:03:06+09:00" level=debug msg="Wrote ping"
any inputs to resolve?creamy-pencil-82913
09/13/2022, 9:35 PM<https://127.0.0.1:2379>
until the etcd pod is up. The second one is normal as things bootstrap; you’ll see it switch the load-balancer tunnel connection over to the new endpoint.magnificent-vr-88571
09/14/2022, 12:24 AMetcd.yaml
from /var/lib/rancher/rke2/agent/pod-manifests
of agent node.
not sure about reason/scenario etcd.yaml
got created in agent node.creamy-pencil-82913
09/15/2022, 11:09 PMmagnificent-vr-88571
09/16/2022, 9:49 PMsystemctl restart rke2-server
it will fail right, since because it can’t find the rke2-server
unit file?creamy-pencil-82913
09/16/2022, 10:15 PMmagnificent-vr-88571
09/16/2022, 10:28 PM-rw-r--r-- 1 root root 11 Jul 5 05:27 /usr/local/lib/systemd/system/rke2-agent.env
-rw-r--r-- 1 root root 870 Jul 5 05:27 /usr/local/lib/systemd/system/rke2-agent.service
-rw-r--r-- 1 root root 11 Jul 5 05:27 /usr/local/lib/systemd/system/rke2-server.env
-rw-r--r-- 1 root root 871 Jul 5 05:27 /usr/local/lib/systemd/system/rke2-server.service
That’s really weird to have it, since because we have an understanding in RKE2 either a node can be server/agent but not both.
I strongly believe there is a possibility of hitting wrong service files both in server and agent nodes.
Irrespective of installer it’s good to have either server
or agent
unit files only to avoid such mishap.creamy-pencil-82913
09/16/2022, 10:45 PMmagnificent-vr-88571
09/16/2022, 10:52 PMcreamy-pencil-82913
09/16/2022, 11:39 PMrke2 server
instead of rke2 agent
, but if you prefer not to have the other files around, you’re free to remove themmagnificent-vr-88571
09/17/2022, 1:03 AMwe do support switching agents to servers by runningsimilarly can we switch servers to agents by runninginstead ofrke2 server
,rke2 agent
rke2 agent
, instead of rke2 server
?creamy-pencil-82913
09/19/2022, 5:30 PMmagnificent-vr-88571
09/19/2022, 5:59 PM