Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: 部署tidb集群过程中,检查集群存在的潜在风险的时候,输入ssh连接密码填完第一台目标服务器之后,没有提示第二次输入密码,直接报错

The image is not visible. Please provide the text you need translated.
Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: 部署tidb集群过程中,检查集群存在的潜在风险的时候,输入ssh连接密码填完第一台目标服务器之后,没有提示第二次输入密码,直接报错
The image is not visible. Please provide the text you need translated.
Must it be consistent? If it’s not consistent, do we need to change it?
Must it be consistent? If it’s not consistent, do we need to change it?
First, change the root password to be consistent. You can restore it after the deployment is completed.
No, the user used to manage the cluster is the one you set in the topology file.
If they are not consistent, set up root mutual trust and password-free login in advance.
I have set up passwordless login with two other machines. Now, the other two can connect, but there is an error indicating that the machine with tiup cannot connect.
I didn’t add the -i option.
tiup cluster check ./topology.yaml --user root [-i /home/root/.ssh/gcp_rsa]
I didn’t use a key to log in. I configured passwordless login directly. Do I still need to use -i?
SSH is not the target machine. I set up the cluster on 194. I can directly SSH from the 194 server to the other two servers.
Password-free authentication is also required for the jump itself.
Set up passwordless SSH for yourself the same way you do for other servers.