Error When Using tiup cluster reload Command

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 用tiup cluster reload 集群报错

| username: TiDBer_bOR8eMEn

[TiDB Usage Environment] Production Environment
[TiDB Version]
Error reported when restarting the cluster using the tiup command. What is the reason for this?

| username: zhanggame1 | Original post link

Is it because of different networks? What result do you get from tiup cluster display?

| username: TiDBer_bOR8eMEn | Original post link

Sorry, I can’t translate the content from the image. Please provide the text you need translated.

| username: zhanggame1 | Original post link

You can see the specific names with tiup cluster list.

| username: TiDBer_bOR8eMEn | Original post link

I know the name of the cluster.

| username: zhanggame1 | Original post link

Run tiup cluster display <cluster-name> to check if everything is normal.

| username: Kongdom | Original post link

Sure, here is the translation:

“Refer to this and take a look
在单机上模拟部署生产环境集群报错: failed to scp - TiDB 的问答社区

| username: TIDB-Learner | Original post link

The cluster already exists, but an error occurs when performing the reload operation after changing the configuration. 1. Check the firewall and SELinux. 2. Check the SSH connectivity from the control machine to each node. 3. If not using root, check file permissions. 4. Check what configuration was changed. Was the cluster functioning normally before?

| username: TiDBer_QYr0vohO | Original post link

It feels like the network or SSH is not working.

| username: jiayou64 | Original post link

You can check the environment:

Block quote

tiup cluster check cluster-name --cluster

Block quote

By specifying the --cluster parameter to switch modes, you can check the deployment machines of the deployed cluster.

| username: Hacker007 | Original post link

Check if passwordless SSH to other nodes is working properly.

| username: Jellybean | Original post link

The error in the screenshot indicates that the configuration file cannot be properly scp’d to the target machine, and an SSH connection cannot be established through port 22.

Check the firewall policies, open ports, and other access issues to ensure that SSH communication between the machines is functioning properly.

| username: lemonade010 | Original post link

tiup cluster list to view the cluster names
tiup cluster display <cluster_name> to view the cluster status