This message was deleted.

The files that do not exist are created when RKE2 starts. If they don’t exist, then RKE2 isn’s starting for some reason. check the rke2-server journald logs for errors.

Hi Bernard thank you for your reply On running sudo journalctl -u rke2-server -f I am getting following logs, What you suggest I can do here Dec 20 100330 node rke2[1677]: {"level":"warn","ts":"2023-12-20T100330.778Z","logger":"etcd-client","caller":"v3@v3.5.7-k3s1/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc000eae000/127.0.0.1:2379","attempt":0,"error":"rpc error: code = DeadlineExceeded desc = latest balancer error: last connection error: connection error: desc = \"transport: authentication handshake failed: tls: failed to verify certificate: x509: certificate signed by unknown authority\""} Dec 20 100330 node rke2[1677]: {"level":"info","ts":"2023-12-20T100330.778Z","logger":"etcd-client","caller":"v3@v3.5.7-k3s1/client.go:210","msg":"Auto sync endpoints failed.","error":"context deadline exceeded"}

Did you already have rke2 or k3s running on this node? The error suggests that there is already an etcd server running on this node, but its certificate is not trusted by RKE2. The only way I can think of this happening is if there is an instance of etcd present that is not managed by rke2.

no, but I tried installing rke2 previously , is there any possibility that it might have caused issue? Do I need to re-install rke2 on a fresh node?

you might run the uninstall script and make sure there’s nothing left over