Some TiDB Components Failed to Install

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

Original topic: tidb 部分组件安装不成功

| username: Cheriston

tidb’s pump drainer offline installation failed

Attention:
1. If the topology is not what you expected, check your yaml file.
2. Please confirm there is no port/directory conflicts in the same host.
Do you want to continue? [y/N]: (default=N) y

  • [ Serial ] - SSHKeySet: privateKey=/root/.tiup/storage/cluster/clusters/test1/ssh/id_rsa, publicKey=/root/.tiup/storage/cluster/clusters/test1/ssh/id_rsa.pub
  • [Parallel] - UserSSH: user=tidb, host=10.10.98.157
  • [Parallel] - UserSSH: user=tidb, host=10.10.98.157
  • [Parallel] - UserSSH: user=tidb, host=10.10.98.158
  • [Parallel] - UserSSH: user=tidb, host=10.10.98.158
  • [Parallel] - UserSSH: user=tidb, host=10.10.98.156
  • [Parallel] - UserSSH: user=tidb, host=10.10.98.157
  • [Parallel] - UserSSH: user=tidb, host=10.10.98.156
  • [Parallel] - UserSSH: user=tidb, host=10.10.98.156
  • Download TiDB components
    • Download pump:v7.2.0 (linux/amd64) … Error
    • Download drainer:v7.2.0 (linux/amd64) … Error

Error: unknown component

Verbose debug logs have been written to /root/.tiup/logs/tiup-cluster-debug-2023-08-17-17-53-44.log.
[root@node156 local]# tail -f /root/.tiup/logs/tiup-cluster-debug-2023-08-17-17-53-44.log
2023-08-17T17:53:44.789+0800 DEBUG TaskBegin {“task”: “Download: component=drainer, version=v7.2.0, os=linux, arch=amd64”}
2023-08-17T17:53:44.789+0800 DEBUG TaskBegin {“task”: “Download: component=pump, version=v7.2.0, os=linux, arch=amd64”}
2023-08-17T17:53:44.789+0800 DEBUG TaskBegin {“task”: “Download: component=drainer, version=v7.2.0, os=linux, arch=amd64”}
2023-08-17T17:53:44.789+0800 DEBUG TaskBegin {“task”: “Download: component=pump, version=v7.2.0, os=linux, arch=amd64”}
2023-08-17T17:53:44.791+0800 DEBUG TaskFinish {“task”: “Download: component=pump, version=v7.2.0, os=linux, arch=amd64”, “error”: “unknown component”, “errorVerbose”: “unknown component\ngithub.com/pingcap/tiup/pkg/repository.init\n\tgithub.com/pingcap/tiup/pkg/repository/v1_repository.go:43\nruntime.doInit\n\truntime/proc.go:6329\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.main\n\truntime/proc.go:233\nruntime.goexit\n\truntime/asm_amd64.s:1594”}
2023-08-17T17:53:44.792+0800 DEBUG TaskFinish {“task”: “Download: component=pump, version=v7.2.0, os=linux, arch=amd64”, “error”: “unknown component”, “errorVerbose”: “unknown component\ngithub.com/pingcap/tiup/pkg/repository.init\n\tgithub.com/pingcap/tiup/pkg/repository/v1_repository.go:43\nruntime.doInit\n\truntime/proc.go:6329\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.main\n\truntime/proc.go:233\nruntime.goexit\n\truntime/asm_amd64.s:1594”}
2023-08-17T17:53:44.792+0800 DEBUG TaskFinish {“task”: “Download: component=drainer, version=v7.2.0, os=linux, arch=amd64”, “error”: “unknown component”, “errorVerbose”: “unknown component\ngithub.com/pingcap/tiup/pkg/repository.init\n\tgithub.com/pingcap/tiup/pkg/repository/v1_repository.go:43\nruntime.doInit\n\truntime/proc.go:6329\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.main\n\truntime/proc.go:233\nruntime.goexit\n\truntime/asm_amd64.s:1594”}
2023-08-17T17:53:44.792+0800 DEBUG TaskFinish {“task”: “Download: component=drainer, version=v7.2.0, os=linux, arch=amd64”, “error”: “unknown component”, “errorVerbose”: “unknown component\ngithub.com/pingcap/tiup/pkg/repository.init\n\tgithub.com/pingcap/tiup/pkg/repository/v1_repository.go:43\nruntime.doInit\n\truntime/proc.go:6329\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.main\n\truntime/proc.go:233\nruntime.goexit\n\truntime/asm_amd64.s:1594”}
2023-08-17T17:53:44.792+0800 DEBUG TaskFinish {“task”: “Download: component=pump, version=v7.2.0, os=linux, arch=amd64\nDownload: component=drainer, version=v7.2.0, os=linux, arch=amd64”, “error”: “unknown component”, “errorVerbose”: “unknown component\ngithub.com/pingcap/tiup/pkg/repository.init\n\tgithub.com/pingcap/tiup/pkg/repository/v1_repository.go:43\nruntime.doInit\n\truntime/proc.go:6329\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.main\n\truntime/proc.go:233\nruntime.goexit\n\truntime/asm_amd64.s:1594”}
2023-08-17T17:53:44.792+0800 INFO Execute command finished {“code”: 1, “error”: “unknown component”, “errorVerbose”: “unknown component\ngithub.com/pingcap/tiup/pkg/repository.init\n\tgithub.com/pingcap/tiup/pkg/repository/v1_repository.go:43\nruntime.doInit\n\truntime/proc.go:6329\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.doInit\n\truntime/proc.go:6306\nruntime.main\n\truntime/proc.go:233\nruntime.goexit\n\truntime/asm_amd64.s:1594”}

| username: zhanggame1 | Original post link

Fa Quan, how did you install it? TiUP?

| username: caiyfc | Original post link

  1. Check where the mirror source is: tiup mirror show
  2. Check if it is an ARM architecture
| username: zhanggame1 | Original post link

Is it an expansion installation? Is the command like this?

| username: ShawnYan | Original post link

It’s similar to what the expert inferred; it’s likely that the private repository used by the original poster doesn’t have pump:v7.2.0.

| username: redgame | Original post link

Check the source, there’s nothing.

| username: Cheriston | Original post link

In an offline environment, the package has been copied into the TiDB installation package.

| username: zhanggame1 | Original post link

Go directly to the installation package directory to see if it exists and if the version number is correct.

| username: Cheriston | Original post link

They are all version 7.3 community edition of Linux.

| username: ShawnYan | Original post link

Simply copying the installation package tiup won’t work, it still can’t be found. Check out this section and create a mirror yourself:

| username: zhanggame1 | Original post link

So why did you install version 7.2?

| username: Cheriston | Original post link

What are the drawbacks?

| username: tidb菜鸟一只 | Original post link

tiup list tidb
Check what can be installed, is it true that pump and drainer are not included at all?

| username: Cheriston | Original post link

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

| username: Cheriston | Original post link

Where is the problem with this? Does anyone know? Please tell me.

tiup cluster deploy test1 v7.1.0 ./topology.yaml --user root -p

| username: caiyfc | Original post link

I am confused by this post.

  1. Initially, the error was reported for version 7.2 with pump and drainer errors. The original poster did not execute tiup mirror show, so it’s impossible to verify if the guess is correct.
  2. The latest reply mentions version 7.1, which seems like a redeployment, but no error information was provided.
| username: Cheriston | Original post link

I tried a new version again:

| username: caiyfc | Original post link

Extract the tarball:

tar xf tidb-community-toolkit-${version}-linux-amd64.tar.gz

List the directories:

ls -ld tidb-community-server-${version}-linux-amd64 tidb-community-toolkit-${version}-linux-amd64

Change to the server directory:

cd tidb-community-server-${version}-linux-amd64/

Copy the keys:

cp -rp keys ~/.tiup/

Merge the toolkit:

tiup mirror merge ../tidb-community-toolkit-${version}-linux-amd64

Deploying a TiDB Cluster Using TiUP | PingCAP Documentation Center

You need to merge the offline package this way, do not directly use cp.

| username: Cheriston | Original post link

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

| username: caiyfc | Original post link

…It’s not enough to just put it in this folder; doing it this way is ineffective: