How to change rke2 data dir

[liyang516]

I deployed a rke2 cluster， with 8 nodes.

Now I want to change rke2 data-dir , from /var/lib/rancher/rke2 to /data/rancher/rke2，what is the steps?
I copy the /var/lib/rancher/rke2 to /data/rancher/, and I restart rke2-server, it failed to start, etcd can not start

[dereknola]

Use the data-dir config flag. https://docs.rke2.io/reference/server_config#common

[liyang516]

Also failed

[brandond]

You're going to need to provide more info than that.

[liyang516]

Sorry，here is my master node rke2-server logs:

11月 05 10:39:45 xcloud17.cpp.zzbm.qianxin-inc.cn rke2[755590]: {"level":"warn","ts":"2024-11-05T10:39:45.710+0800","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc015dd0c40/127.0.0.1:2379","attempt":0,"error":"rpc error: code = DeadlineExceeded desc = latest balancer error: last connection error: connection error: desc = \"transport: Error while dialing dial tcp 127.0.0.1:2379: connect: connection refused\""}
11月 05 10:39:45 xcloud17.cpp.zzbm.qianxin-inc.cn rke2[755590]: time="2024-11-05T10:39:45+08:00" level=info msg="Failed to test data store connection: context deadline exceeded"
11月 05 10:39:50 xcloud17.cpp.zzbm.qianxin-inc.cn rke2[755590]: time="2024-11-05T10:39:50+08:00" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://127.0.0.1:9345/v1-rke2/readyz: 500 Internal Server Error"
11月 05 10:39:55 xcloud17.cpp.zzbm.qianxin-inc.cn rke2[755590]: time="2024-11-05T10:39:55+08:00" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://127.0.0.1:9345/v1-rke2/readyz: 500 Internal Server Error"
11月 05 10:40:00 xcloud17.cpp.zzbm.qianxin-inc.cn rke2[755590]: time="2024-11-05T10:40:00+08:00" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://127.0.0.1:9345/v1-rke2/readyz: 500 Internal Server Error"
11月 05 10:40:00 xcloud17.cpp.zzbm.qianxin-inc.cn rke2[755590]: {"level":"warn","ts":"2024-11-05T10:40:00.711+0800","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc015dd0c40/127.0.0.1:2379","attempt":0,"error":"rpc error: code = DeadlineExceeded desc = latest balancer error: last connection error: connection error: desc = \"transport: Error while dialing dial tcp 127.0.0.1:2379: connect: connection refused\""}
11月 05 10:40:00 xcloud17.cpp.zzbm.qianxin-inc.cn rke2[755590]: time="2024-11-05T10:40:00+08:00" level=info msg="Failed to test data store connection: context deadline exceeded"
11月 05 10:40:05 xcloud17.cpp.zzbm.qianxin-inc.cn rke2[755590]: time="2024-11-05T10:40:05+08:00" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://127.0.0.1:9345/v1-rke2/readyz: 500 Internal Server Error"
11月 05 10:40:05 xcloud17.cpp.zzbm.qianxin-inc.cn rke2[755590]: time="2024-11-05T10:40:05+08:00" level=info msg="Waiting for etcd server to become available"
11月 05 10:40:05 xcloud17.cpp.zzbm.qianxin-inc.cn rke2[755590]: time="2024-11-05T10:40:05+08:00" level=info msg="Waiting for API server to become available"
11月 05 10:40:10 xcloud17.cpp.zzbm.qianxin-inc.cn rke2[755590]: {"level":"warn","ts":"2024-11-05T10:40:10.279+0800","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc015dd0c40/127.0.0.1:2379","attempt":0,"error":"rpc error: code = DeadlineExceeded desc = latest balancer error: last connection error: connection error: desc = \"transport: Error while dialing dial tcp 127.0.0.1:2379: connect: connection refused\""}
11月 05 10:40:10 xcloud17.cpp.zzbm.qianxin-inc.cn rke2[755590]: time="2024-11-05T10:40:10+08:00" level=error msg="Failed to check local etcd status for learner management: context deadline exceeded"
11月 05 10:40:10 xcloud17.cpp.zzbm.qianxin-inc.cn rke2[755590]: time="2024-11-05T10:40:10+08:00" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://127.0.0.1:9345/v1-rke2/readyz: 500 Internal Server Error"
11月 05 10:40:15 xcloud17.cpp.zzbm.qianxin-inc.cn rke2[755590]: time="2024-11-05T10:40:15+08:00" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://127.0.0.1:9345/v1-rke2/readyz: 500 Internal Server Error"
11月 05 10:40:15 xcloud17.cpp.zzbm.qianxin-inc.cn rke2[755590]: {"level":"warn","ts":"2024-11-05T10:40:15.712+0800","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc015dd0c40/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: read tcp 127.0.0.1:37596->127.0.0.1:2379: read: connection reset by peer\""}
11月 05 10:40:15 xcloud17.cpp.zzbm.qianxin-inc.cn rke2[755590]: time="2024-11-05T10:40:15+08:00" level=info msg="Failed to test data store connection: context deadline exceeded"

[brandond]

Look at the pod logs to see what is wrong. Are you by any chance running with selinux?