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