在单机上模拟部署生产环境集群报错：ssh_stderr: Failed to enable unit: Unit file pd-2379.service does not exist

TiDBer_oHpB1az2 · 2023 年6 月 17 日 03:50

OS: Fedora Linux 38 (Workstation Edition) x86_64
Kernel: 6.3.7-200.fc38.x86_64

$ tiup cluster deploy tidb_local v7.1.0 ./topo.yaml --user root -p
tiup is checking updates for component cluster ...
Starting component `cluster`: /home/user/.tiup/components/cluster/v1.12.3/tiup-cluster deploy tidb_local v7.1.0 ./topo.yaml --user root -p
Input SSH password: 

+ Detect CPU Arch Name
  - Detecting node 172.21.117.108 Arch info ... Done

+ Detect CPU OS Name
  - Detecting node 172.21.117.108 OS info ... Done
Please confirm your topology:
Cluster type:    tidb
Cluster name:    tidb_local
Cluster version: v7.1.0
Role        Host            Ports                            OS/Arch       Directories
----        ----            -----                            -------       -----------
pd          172.21.117.108  2379/2380                        linux/x86_64  /data/tidb/deploy/pd-2379,/data/tidb/data/pd-2379
tikv        172.21.117.108  20160/20180                      linux/x86_64  /data/tidb/deploy/tikv-20160,/data/tidb/data/tikv-20160
tikv        172.21.117.108  20161/20181                      linux/x86_64  /data/tidb/deploy/tikv-20161,/data/tidb/data/tikv-20161
tikv        172.21.117.108  20162/20182                      linux/x86_64  /data/tidb/deploy/tikv-20162,/data/tidb/data/tikv-20162
tidb        172.21.117.108  4000/10080                       linux/x86_64  /data/tidb/deploy/tidb-4000
tiflash     172.21.117.108  9000/8123/3930/20170/20292/8234  linux/x86_64  /data/tidb/deploy/tiflash-9000,/data/tidb/data/tiflash-9000
prometheus  172.21.117.108  9090/12020                       linux/x86_64  /data/tidb/deploy/prometheus-9090,/data/tidb/data/prometheus-9090
grafana     172.21.117.108  3000                             linux/x86_64  /data/tidb/deploy/grafana-3000
Attention:
    1. If the topology is not what you expected, check your yaml file.
    2. Please confirm there is no port/directory conflicts in same host.
Do you want to continue? [y/N]: (default=N) y
+ Generate SSH keys ... Done
+ Download TiDB components
  - Download pd:v7.1.0 (linux/amd64) ... Done
  - Download tikv:v7.1.0 (linux/amd64) ... Done
  - Download tidb:v7.1.0 (linux/amd64) ... Done
  - Download tiflash:v7.1.0 (linux/amd64) ... Done
  - Download prometheus:v7.1.0 (linux/amd64) ... Done
  - Download grafana:v7.1.0 (linux/amd64) ... Done
  - Download node_exporter: (linux/amd64) ... Done
  - Download blackbox_exporter: (linux/amd64) ... Done
+ Initialize target host environments
  - Prepare 172.21.117.108:22 ... Done
+ Deploy TiDB instance
  - Copy pd -> 172.21.117.108 ... Done
  - Copy tikv -> 172.21.117.108 ... Done
  - Copy tikv -> 172.21.117.108 ... Done
  - Copy tikv -> 172.21.117.108 ... Done
  - Copy tidb -> 172.21.117.108 ... Done
  - Copy tiflash -> 172.21.117.108 ... Done
  - Copy prometheus -> 172.21.117.108 ... Done
  - Copy grafana -> 172.21.117.108 ... Done
  - Deploy node_exporter -> 172.21.117.108 ... Done
  - Deploy blackbox_exporter -> 172.21.117.108 ... Done
+ Copy certificate to remote host
+ Init instance configs
  - Generate config pd -> 172.21.117.108:2379 ... Done
  - Generate config tikv -> 172.21.117.108:20160 ... Done
  - Generate config tikv -> 172.21.117.108:20161 ... Done
  - Generate config tikv -> 172.21.117.108:20162 ... Done
  - Generate config tidb -> 172.21.117.108:4000 ... Done
  - Generate config tiflash -> 172.21.117.108:9000 ... Done
  - Generate config prometheus -> 172.21.117.108:9090 ... Done
  - Generate config grafana -> 172.21.117.108:3000 ... Done
+ Init monitor configs
  - Generate config node_exporter -> 172.21.117.108 ... Done
  - Generate config blackbox_exporter -> 172.21.117.108 ... Done
Enabling component pd
	Enabling instance 172.21.117.108:2379
Failed to enable unit: Unit file pd-2379.service does not exist.


Error: failed to enable/disable pd: failed to enable: 172.21.117.108 pd-2379.service, please check the instance's log(/data/tidb/deploy/pd-2379/log) for more detail.: executor.ssh.execute_failed: Failed to execute command over SSH for 'tidb@172.21.117.108:22' {ssh_stderr: Failed to enable unit: Unit file pd-2379.service does not exist.
, ssh_stdout: , ssh_command: export LANG=C; PATH=$PATH:/bin:/sbin:/usr/bin:/usr/sbin /usr/bin/sudo -H bash -c "systemctl daemon-reload && systemctl enable pd-2379.service"}, cause: Process exited with status 1

zhanggame1 · 2023 年6 月 17 日 04:14

看看日志/data/tidb/deploy/pd-2379/log里面还有其他内容吗

zhanggame1 · 2023 年6 月 17 日 04:46

部署建议参考官方文档
使用 TiUP 部署 TiDB 集群 | PingCAP 文档中心
在部署前作一次检查修复，看看有没有什么问题
tiup cluster check ./topology.yaml --apply --user root -p

redgame · 2023 年6 月 17 日 11:26

ssh服务有问题，建议重装下ssh

Anna · 2023 年6 月 18 日 16:40

你看ssh没连上

TiDBer_oHpB1az2 · 2023 年6 月 19 日 01:03

$ tiup cluster check ./topo.yaml --apply --user root -p
tiup is checking updates for component cluster …
Starting component cluster: /home/user/.tiup/components/cluster/v1.12.3/tiup-cluster check ./topo.yaml --apply --user root -p
Input SSH password:

Detect CPU Arch Name
- Detecting node 172.21.117.108 Arch info … Done
Detect CPU OS Name
- Detecting node 172.21.117.108 OS info … Done
Download necessary tools
- Downloading check tools for linux/amd64 … Done
Collect basic system information
Collect basic system information
- Getting system info of 172.21.117.108:22 … Done
Check time zone
- Checking node 172.21.117.108 … Done
Check system requirements
Check system requirements
Check system requirements
Check system requirements
- Checking node 172.21.117.108 … Done
- Checking node 172.21.117.108 … Done
- Checking node 172.21.117.108 … Done
- Checking node 172.21.117.108 … Done
- Checking node 172.21.117.108 … Done
- Checking node 172.21.117.108 … Done
- Checking node 172.21.117.108 … Done
- Checking node 172.21.117.108 … Done
- Checking node 172.21.117.108 … Done
Cleanup check files
- Cleanup check files on 172.21.117.108:22 … Done
  Node Check Result Message

172.21.117.108 sysctl 172.21.117.108 sysctl 172.21.117.108 sysctl 172.21.117.108 thp 172.21.117.108 service 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 exist 172.21.117.108 memory 172.21.117.108 limits 172.21.117.108 limits 172.21.117.108 limits 172.21.117.108 selinux 172.21.117.108 os-version 172.21.117.108 command 172.21.117.108 172.21.117.108 disk 172.21.117.108 disk 172.21.117.108 disk 172.21.117.108 cpu-cores 172.21.117.108 cpu-governor 172.21.117.108 swap 172.21.117.108 network 172.21.117.108 network 172.21.117.108 network 172.21.117.108 network 172.21.117.108 network 172.21.117.108 network Fail will try to set ‘net.core.somaxconn = 32768’
Fail will try to set ‘net.ipv4.tcp_syncookies = 0’
Fail will try to set ‘vm.swappiness = 0’
Fail will try to disable THP, please check again after reboot
Fail service irqbalance not found, should be installed and started
Fail /etc/systemd/system/tikv-20160.service already exists, auto fixing not supported
Fail /etc/systemd/system/tiflash-9000.service already exists, auto fixing not supported
Fail /etc/systemd/system/tikv-20161.service already exists, auto fixing not supported
Fail /data/tidb/data/prometheus-9090 already exists, auto fixing not supported
Fail /data/tidb/data/tikv-20160 already exists, auto fixing not supported
Fail /data/tidb/deploy/tikv-20160/log already exists, auto fixing not supported
Fail /data/tidb/deploy/tikv-20162/log already exists, auto fixing not supported
Fail /data/tidb/deploy/tikv-20161/log already exists, auto fixing not supported
Fail /data/tidb/deploy/tidb-4000 already exists, auto fixing not supported
Fail /etc/systemd/system/prometheus-9090.service already exists, auto fixing not supported
Fail /data/tidb/deploy/tikv-20160 already exists, auto fixing not supported
Fail /data/tidb/data/tikv-20161 already exists, auto fixing not supported
Fail /etc/systemd/system/tikv-20162.service already exists, auto fixing not supported
Fail /data/tidb/data/tiflash-9000 already exists, auto fixing not supported
Fail /data/tidb/data/pd-2379 already exists, auto fixing not supported
Fail /data/tidb/deploy/tiflash-9000 already exists, auto fixing not supported
Fail /data/tidb/deploy/pd-2379/log already exists, auto fixing not supported
Fail /data/tidb/deploy/tiflash-9000/log already exists, auto fixing not supported
Fail /data/tidb/deploy/prometheus-9090 already exists, auto fixing not supported
Fail /etc/systemd/system/tidb-4000.service already exists, auto fixing not supported
Fail /data/tidb/deploy/prometheus-9090/log already exists, auto fixing not supported
Fail /data/tidb/deploy/tikv-20161 already exists, auto fixing not supported
Fail /data/tidb/deploy/pd-2379 already exists, auto fixing not supported
Fail /etc/systemd/system/pd-2379.service already exists, auto fixing not supported
Fail /data/tidb/deploy/grafana-3000 already exists, auto fixing not supported
Fail /data/tidb/deploy/tidb-4000/log already exists, auto fixing not supported
Fail /data/tidb/deploy/grafana-3000/log already exists, auto fixing not supported
Fail /etc/systemd/system/grafana-3000.service already exists, auto fixing not supported
Fail /data/tidb/deploy/tikv-20162 already exists, auto fixing not supported
Fail /data/tidb/data/tikv-20162 already exists, auto fixing not supported
Pass memory size is 32768MB
Fail will try to set ‘tidb soft nofile 1000000’
Fail will try to set ‘tidb hard nofile 1000000’
Fail will try to set ‘tidb soft stack 10240’
Fail will try to disable SELinux, reboot might be needed
Fail os vendor fedora not supported, auto fixing not supported
Fail numactl not usable, bash: numactl: command not found, auto fixing not supported
listening-port Fail port 3000 is already in use, auto fixing not supported
Fail mount point /data does not have ‘nodelalloc’ option set, auto fixing not supported
Fail multiple components tikv:/data/tidb/data/tikv-20160,tikv:/data/tidb/data/tikv-20161,tikv:/data/tidb/data/tikv-20162,tiflash:/data/tidb/data/tiflash-9000 are using the same partition 172.21.117.108:/data as data dir, auto fixing not supported
Warn mount point /data does not have ‘noatime’ option set, auto fixing not supported
Pass number of CPU cores / threads: 16
Fail CPU frequency governor is powersave, should use performance, auto fixing not supported
Warn will try to disable swap, please also check /etc/fstab manually
Pass network speed of enp2s0 is 10000MB
Pass network speed of veth8e29ecf is 10000MB
Pass network speed of veth919b5c7 is 10000MB
Pass network speed of vethcb63708 is 10000MB
Pass network speed of docker0 is 10000MB
Pass network speed of eno1 is 1000MB

Try to apply changes to fix failed checks
Try to apply changes to fix failed checks
Try to apply changes to fix failed checks
- Applying changes on 172.21.117.108 … Done

zhanggame1 · 2023 年6 月 19 日 01:41

还没装过去吗？先destroy再重装试试

xingzhenxiang · 2023 年6 月 19 日 01:42

重新安装一下试试

TiDBer_oHpB1az2 · 2023 年6 月 19 日 08:09

@zhanggame1 经过测试，tiup在centos上的确可以做到一键部署。
但fedora上不行。期待tidb改进部署和运维体验。谢谢

zhanggame1 · 2023 年6 月 19 日 08:13

我用的最新的Ubuntu 22.04.2 LTS测试也没问题，ceonts7马上停止服务了，所以我们生产业务打算部署到Ubuntu上

TiDBer_oHpB1az2 · 2023 年6 月 19 日 08:18

可否麻烦测试下fedora 38?

TiDBer_oHpB1az2 · 2023 年6 月 19 日 08:41

另外，不知对centos 9 stream支持度怎么样？我正准备测试下

buptzhoutian · 2023 年6 月 19 日 09:02

不是 SSH 连接问题(SSH通道是好的前面拷贝文件都成功了)，是通过 SSH 执行这个命令的时候报错了，你可以到机器上看看这个 systemd unit 是啥情况。

TiDBer_ZevpzaDp · 2023 年10 月 9 日 01:32

请问SSH密码应该怎么获取啊

TiDBer_小阿飞 · 2023 年10 月 9 日 02:09

OS: Fedora Linux 38 (Workstation Edition) x86_64
是否支持此操作系统啊？

Billmay表妹 · 2023 年10 月 9 日 02:18

https://docs.pingcap.com/zh/tidb/stable/hardware-and-software-requirements

可以查看这个文档。

system · 2023 年12 月 8 日 02:18

此话题已在最后回复的 60 天后被自动关闭。不再允许新回复。