PD server timeout after using pd-recover

## Bug Report

### What did you do?

After reinstalling the machine and executing pd-recover, create a table that returns PD server timeout.

### What did you expect to see?

No error

### What did you see instead?
[2023/09/26 09:57:48.190 +08:00] [WARN] [proxy.go:193] ["fail to recv activity from remote, stay inactive and wait to next checking round"] [remote=192.168.1.70:4000] [interval=2s] [error="dial tcp 192.168.1.70:4000: connect: connection refused"]
[2023/09/26 09:57:48.190 +08:00] [WARN] [proxy.go:193] ["fail to recv activity from remote, stay inactive and wait to next checking round"] [remote=192.168.1.70:10080] [interval=2s] [error="dial tcp 192.168.1.70:10080: connect: connection refused"]
[2023/09/26 09:57:50.191 +08:00] [WARN] [proxy.go:193] ["fail to recv activity from remote, stay inactive and wait to next checking round"] [remote=192.168.1.70:10080] [interval=2s] [error="dial tcp 192.168.1.70:10080: connect: connection refused"]
[2023/09/26 09:57:50.191 +08:00] [WARN] [proxy.go:193] ["fail to recv activity from remote, stay inactive and wait to next checking round"] [remote=192.168.1.70:4000] [interval=2s] [error="dial tcp 192.168.1.70:4000: connect: connection refused"]
### What version of PD are you using (`pd-server -V`)?
pd-server-V7.1.1