tiup部署后,启动PD失败问题
@lucklove is already working on this.
Since Nov 23, 2020.
- Dominant language
- Python
- Stars
- 1.8k
- Forks
- 1.2k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 31
Description
File: /production-deployment-using-tiup.md
[tidb@chad2 scripts]$ tiup cluster display tidb-test
Found cluster newer version:
The latest version: v1.2.4
Local installed version: v1.2.3
Update current component: tiup update cluster
Update all components: tiup update --all
Starting component cluster: /home/tidb/.tiup/components/cluster/v1.2.3/tiup-cluster display tidb-test
Cluster type: tidb
Cluster name: tidb-test
Cluster version: v4.0.8
SSH type: builtin
ID Role Host Ports OS/Arch Status Data Dir Deploy Dir
192.168.3.126:9093 alertmanager 192.168.3.126 9093/9094 linux/x86_64 inactive /tidb-data/alertmanager-9093 /tidb-deploy/alertmanager-9093
192.168.3.126:3000 grafana 192.168.3.126 3000 linux/x86_64 inactive - /tidb-deploy/grafana-3000
192.168.3.126:2379 pd 192.168.3.126 2379/2380 linux/x86_64 Down /tidb-data/pd-2379 /tidb-deploy/pd-2379
192.168.3.126:2479 pd 192.168.3.126 2479/2381 linux/x86_64 Down /tidb-data/pd-2479 /tidb-deploy/pd-2479
192.168.3.130:2379 pd 192.168.3.130 2379/2380 linux/x86_64 Down /tidb-data/pd-2379 /tidb-deploy/pd-2379
192.168.3.126:9090 prometheus 192.168.3.126 9090 linux/x86_64 inactive /tidb-data/prometheus-9090 /tidb-deploy/prometheus-9090
192.168.3.126:4000 tidb 192.168.3.126 4000/10080 linux/x86_64 Down - /tidb-deploy/tidb-4000
192.168.3.126:4001 tidb 192.168.3.126 4001/10081 linux/x86_64 Down - /tidb-deploy/tidb-4001
192.168.3.130:4000 tidb 192.168.3.130 4000/10080 linux/x86_64 Down - /tidb-deploy/tidb-4000
192.168.3.126:20160 tikv 192.168.3.126 20160/20180 linux/x86_64 Down /tidb-data/tikv-20160 /tidb-deploy/tikv-20160
192.168.3.126:20161 tikv 192.168.3.126 20161/20181 linux/x86_64 Down /tidb-data/tikv-20161 /tidb-deploy/tikv-20161
192.168.3.130:20160 tikv 192.168.3.130 20160/20180 linux/x86_64 Down /tidb-data/tikv-20160 /tidb-deploy/tikv-20160
Total nodes: 12
WARN: get location labels from pd failed: no endpoint available, the last err is: Get http://192.168.3.130:2379/pd/api/v1/config/replicate: dial tcp 192.168.3.130:2379: connect: connection refused
[tidb@chad2 scripts]$
[tidb@chad2 scripts]$ cd $HOME
[tidb@chad2 ~]$ ls
logs topology.yaml
[tidb@chad2 ~]$ vi topology.yaml
[tidb@chad2 ~]$ tiup cluster start tidb-test
Found cluster newer version:
The latest version: v1.2.4
Local installed version: v1.2.3
Update current component: tiup update cluster
Update all components: tiup update --all
Starting component cluster: /home/tidb/.tiup/components/cluster/v1.2.3/tiup-cluster start tidb-test
Starting cluster tidb-test...
- [ Serial ] - SSHKeySet: privateKey=/home/tidb/.tiup/storage/cluster/clusters/tidb-test/ssh/id_rsa, publicKey=/home/tidb/.tiup/storage/cluster/clusters/tidb-test/ssh/id_rsa.pub
- [Parallel] - UserSSH: user=tidb, host=192.168.3.126
- [Parallel] - UserSSH: user=tidb, host=192.168.3.126
- [Parallel] - UserSSH: user=tidb, host=192.168.3.126
- [Parallel] - UserSSH: user=tidb, host=192.168.3.126
- [Parallel] - UserSSH: user=tidb, host=192.168.3.130
- [Parallel] - UserSSH: user=tidb, host=192.168.3.126
- [Parallel] - UserSSH: user=tidb, host=192.168.3.126
- [Parallel] - UserSSH: user=tidb, host=192.168.3.126
- [Parallel] - UserSSH: user=tidb, host=192.168.3.130
- [Parallel] - UserSSH: user=tidb, host=192.168.3.126
- [Parallel] - UserSSH: user=tidb, host=192.168.3.130
- [Parallel] - UserSSH: user=tidb, host=192.168.3.126
- [ Serial ] - StartCluster
Starting component pd
Starting instance pd 192.168.3.130:2379
Starting instance pd 192.168.3.126:2379
Starting instance pd 192.168.3.126:2479
retry error: operation timed out after 2m0s
pd 192.168.3.126:2479 failed to start: timed out waiting for port 2479 to be started after 2m0s, please check the log of the instance
retry error: operation timed out after 2m0s
pd 192.168.3.126:2379 failed to start: timed out waiting for port 2379 to be started after 2m0s, please check the log of the instance
retry error: operation timed out after 2m0s
pd 192.168.3.130:2379 failed to start: timed out waiting for port 2379 to be started after 2m0s, please check the log of the instance
Error: failed to start pd: pd 192.168.3.126:2479 failed to start: timed out waiting for port 2479 to be started after 2m0s, please check the log of the instance: timed out waiting for port 2479 to be started after 2m0s
Verbose debug logs has been written to /home/tidb/logs/tiup-cluster-debug-2020-11-19-08-49-56.log.
Error: run /home/tidb/.tiup/components/cluster/v1.2.3/tiup-cluster (wd:/home/tidb/.tiup/data/SGnKbQ5) failed: exit status 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.