During the deployment of the TiDB cluster, when checking for potential risks in the cluster, after entering the SSH connection password for the first target server, there is no prompt to enter the password a second time, and an error is reported directly

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

Original topic: 部署tidb集群过程中,检查集群存在的潜在风险的时候,输入ssh连接密码填完第一台目标服务器之后,没有提示第二次输入密码,直接报错

| username: 朵拉大虾

The image is not visible. Please provide the text you need translated.

| username: caiyfc | Original post link

Is the root password the same? Is the firewall enabled?

| username: xingzhenxiang | Original post link

Are the passwords consistent across the cluster?

| username: 朵拉大虾 | Original post link

Must it be consistent? If it’s not consistent, do we need to change it?

| username: 朵拉大虾 | Original post link

Must it be consistent? If it’s not consistent, do we need to change it?

| username: caiyfc | Original post link

First, change the root password to be consistent. You can restore it after the deployment is completed.

| username: 朵拉大虾 | Original post link

Will restoring it again affect the already built cluster?

| username: caiyfc | Original post link

No, the user used to manage the cluster is the one you set in the topology file.

| username: xingzhenxiang | Original post link

If they are not consistent, set up root mutual trust and password-free login in advance.

| username: 朵拉大虾 | Original post link

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.

| username: xingzhenxiang | Original post link

I didn’t add the -i option.

tiup cluster check ./topology.yaml --user root [-i /home/root/.ssh/gcp_rsa]

| username: 朵拉大虾 | Original post link

I didn’t use a key to log in. I configured passwordless login directly. Do I still need to use -i?

| username: 像风一样的男子 | Original post link

Can you directly SSH to 192.168.0.194 and get through?

| username: 朵拉大虾 | Original post link

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.

| username: 像风一样的男子 | Original post link

Password-free authentication is also required for the jump itself.

| username: tidb狂热爱好者 | Original post link

You haven’t set up the SSH network yet.

| username: 朵拉大虾 | Original post link

How to implement this redirection…

| username: 朵拉大虾 | Original post link

Now you can directly connect to the other two servers.

| username: 像风一样的男子 | Original post link

Set up passwordless SSH for yourself the same way you do for other servers.

| username: 朵拉大虾 | Original post link

Got it, thanks.