can not start tidb cluster though tidb-ansible

[OnePython]

243挂掉以后，tidb服务无法启动。 下面是配置文件：

TiDB Cluster Part

[tidb_servers] 192.168.0.241 192.168.0.242

[pd_servers] 192.168.0.241 192.168.0.242 192.168.0.243

[tikv_servers] 192.168.0.242 192.168.0.243 192.168.0.244

[spark_master]

[spark_slaves]

[lightning_server]

[importer_server]

[monitoring_servers] 192.168.0.241

[grafana_servers] 192.168.0.241

[monitored_servers] 192.168.0.241 192.168.0.242 192.168.0.243 192.168.0.244

[alertmanager_servers] 192.168.0.241

[kafka_exporter_servers]

[pump_servers]

[drainer_servers]

[pd_servers:vars]

[all:vars] deploy_dir = /home/tidb/deploy

下面是错误日志：

2019-08-14 10:05:15,228 p=13107 u=tidb | TASK [start TiDB by supervise] * 2019-08-14 10:05:15,369 p=13107 u=tidb | TASK [start TiDB by systemd] *** 2019-08-14 10:05:17,369 p=13107 u=tidb | ok: [192.168.0.242] 2019-08-14 10:05:19,291 p=13107 u=tidb | ok: [192.168.0.241] 2019-08-14 10:05:19,298 p=13107 u=tidb | TASK [wait until the TiDB port is up] ** 2019-08-14 10:10:21,060 p=13107 u=tidb | fatal: [192.168.0.242]: FAILED! => {"changed": false, "elapsed": 300, "msg": "the TiDB port 4000 is not up"} 2019-08-14 10:10:21,069 fail [192.168.0.242]: Ansible FAILED! => playbook: start.yml; TASK: wait until the TiDB port is up; message: {"changed": false, "elapsed": 300, "msg": "the TiDB port 4000 is not up"} 2019-08-14 10:10:21,074 p=13107 u=tidb | fatal: [192.168.0.241]: FAILED! => {"changed": false, "elapsed": 300, "msg": "the TiDB port 4000 is not up"} 2019-08-14 10:10:21,075 fail [192.168.0.241]: Ansible FAILED! => playbook: start.yml; TASK: wait until the TiDB port is up; message: {"changed": false, "elapsed": 300, "msg": "the TiDB port 4000 is not up"} 2019-08-14 10:10:21,082 p=13107 u=tidb | to retry, use: --limit @/home/tidb/tidb-ansible/retry_files/start.retry

2019-08-14 10:10:21,082 p=13107 u=tidb | PLAY RECAP ***** 2019-08-14 10:10:21,082 p=13107 u=tidb | 192.168.0.241 : ok=22 changed=0 unreachable=0 failed=1
2019-08-14 10:10:21,082 p=13107 u=tidb | 192.168.0.242 : ok=18 changed=0 unreachable=0 failed=1
2019-08-14 10:10:21,082 p=13107 u=tidb | 192.168.0.243 : ok=17 changed=0 unreachable=0 failed=0
2019-08-14 10:10:21,082 p=13107 u=tidb | 192.168.0.244 : ok=14 changed=0 unreachable=0 failed=0
2019-08-14 10:10:21,084 p=13107 u=tidb | ERROR MESSAGE SUMMARY ** 2019-08-14 10:10:21,090 p=13107 u=tidb | [192.168.0.242]: Ansible FAILED! => playbook: start.yml; TASK: wait until the TiDB port is up; message: {"changed": false, "elapsed": 300, "msg": "the TiDB port 4000 is not up"}

2019-08-14 10:10:21,090 p=13107 u=tidb | [192.168.0.241]: Ansible FAILED! => playbook: start.yml; TASK: wait until the TiDB port is up; message: {"changed": false, "elapsed": 300, "msg": "the TiDB port 4000 is not up"}

2019-08-14 10:10:21,090 p=13107 u=tidb | Ask for help: 2019-08-14 10:10:21,090 p=13107 u=tidb | Contact us: support@pingcap.com 2019-08-14 10:10:21,091 p=13107 u=tidb | It seems that you encounter some problems. You can send an email to the above email address, attached with the tidb-ansible/inventory.ini and tidb-ansible/log/ansible.log files and the error message, or new issue on https://github.com/pingcap/tidb-ansible/issues. We'll try our best to help you deploy a TiDB cluster. Thanks. :-)

[zz-jason]

@OnePython Could you post the tikv and tidb logs here to help us investigate the problem?

[zz-jason]

What's the tidb version are you using? Is the cluster rolling updated from an old version?

[zz-jason]

close due to no update for a long time.