Error Occurred During Deployment Using TIUP

Translated
1

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

Original topic: 使用TIUP部署时报错

| username: TiDBer_EYdbxOAS

Prerequisites:

  1. The topology file has been configured;
  2. 160 is the deployment host, 159, 161, and 162 are the other three machines, the keys have been established, and the authorized_keys file has been placed on the corresponding three machines;
  3. From 160, all three machines can be pinged, and the ports are open;
  4. From 160, you can log in to the other three machines via SSH;
    Can the experts take a look at how to solve the problem?
    Additionally, after removing the :
    image
    image1561×558 41.5 KB

    Key path:
    image
2
| username: WalterWj | Original post link

-i does not need to use .

3
| username: Jolyne | Original post link

tiup cluster deploy tidb-test v7.5.0 ./topology.yaml --user root -i /home/root/.ssh/gcp_rsa (replace with your path)

4
| username: zhanggame1 | Original post link

The square brackets are useless. It’s more convenient to use the root account for installation, no need to configure mutual trust.

5
| username: TiDBer_EYdbxOAS | Original post link

Changing [-i] to -i still doesn’t work.

6
| username: TiDBer_EYdbxOAS | Original post link

Do multiple machines in the cluster need a root account, and do the passwords for root need to be consistent?

7
| username: TiDBer_EYdbxOAS | Original post link

The path has actually been changed to my own path, which is the path of the public key, but I didn’t use the root user.

8
| username: Jolyne | Original post link

You need to keep your SSH password consistent, and do you have a TiDB user?

9
| username: zhanggame1 | Original post link

Root deployment can be done with user root -p, no need for -i and such, and no need to configure mutual trust. All machines need to have the same root password.

10
| username: TiDBer_EYdbxOAS | Original post link

What does it mean for the SSH password to remain consistent? Does it mean that the login passwords for non-root users in the cluster also need to be consistent?

11
| username: 普罗米修斯 | Original post link

Is the error still related to SSH authentication? Are the other three servers working fine with SSH passwordless login? Also, have you added the ordinary user operation permissions in the sudoers file?

12
| username: TiDBer_EYdbxOAS | Original post link

SSH login to the other three servers is normal and does not require entering the corresponding target machine’s password.

image
image1135×727 38.4 KB

On the corresponding three machines, the authorized_keys file was generated using the ssh-copy-id user@target_host command.

13
| username: TiDBer_小阿飞 | Original post link

It’s probably a trust issue, configure mutual trust.

14
| username: 普罗米修斯 | Original post link

What is this? Do I still need to input something?
Normally, password-free setup should look like this:
图片

15
| username: 普罗米修斯 | Original post link

Take a look at this sshd configuration.

16
| username: Miracle | Original post link

Did you set a password for id_rsa? What needs to be entered after ssh in this picture?

17
| username: TiDBer_EYdbxOAS | Original post link

I reset the mutual trust again, and now it has been completed.

image
image1126×741 37.4 KB

However, when checking for potential risks in the cluster, an error was reported. The error looks quite similar to the previous one.
image
image1561×456 32.3 KB

18
| username: 小龙虾爱大龙虾 | Original post link

For the SSH issue, try connecting manually. If that doesn’t work, make sure all password configurations are the same, then just enter the password.

19
| username: 随缘天空 | Original post link

No need for the -i parameter, tiup supports passwordless mutual trust by default.

20
| username: dba远航 | Original post link

Try connecting manually to troubleshoot the SSH issue.