为提高效率，提问时请提供以下信息，问题描述清晰可优先响应。
- 【TiDB 版本】：tidb-ansible-3.0.2
- 【问题描述】：离线 TiDB Ansible 部署
在中控机执行 ansible-playbook -i hosts.ini deploy_ntp.yml -u tidb -b报错如下：
TASK [Adjust Time | start to adjust time with 192.168.80.151] ******************************************************************************************
fatal: [192.168.80.152]: FAILED! => {“changed”: true, “cmd”: “ntpdate 192.168.80.151”, “delta”: “0:00:08.105450”, “end”: “2019-12-17 17:27:55.479743”, “msg”: “non-zero return code”, “rc”: 1, “start”: “2019-12-17 17:27:47.374293”, “stderr”: “17 Dec 17:27:55 ntpdate[5507]: no server suitable for synchronization found”, “stderr_lines”: [“17 Dec 17:27:55 ntpdate[5507]: no server suitable for synchronization found”], “stdout”: “”, “stdout_lines”: []}
fatal: [192.168.80.153]: FAILED! => {“changed”: true, “cmd”: “ntpdate 192.168.80.151”, “delta”: “0:00:08.105985”, “end”: “2019-12-17 17:27:55.512040”, “msg”: “non-zero return code”, “rc”: 1, “start”: “2019-12-17 17:27:47.406055”, “stderr”: “17 Dec 17:27:55 ntpdate[5544]: no server suitable for synchronization found”, “stderr_lines”: [“17 Dec 17:27:55 ntpdate[5544]: no server suitable for synchronization found”], “stdout”: “”, “stdout_lines”: []}
fatal: [192.168.80.151]: FAILED! => {“changed”: true, “cmd”: “ntpdate 192.168.80.151”, “delta”: “0:00:08.105045”, “end”: “2019-12-17 17:27:55.545592”, “msg”: “non-zero return code”, “rc”: 1, “start”: “2019-12-17 17:27:47.440547”, “stderr”: “17 Dec 17:27:55 ntpdate[6940]: no server suitable for synchronization found”, “stderr_lines”: [“17 Dec 17:27:55 ntpdate[6940]: no server suitable for synchronization found”], “stdout”: “”, “stdout_lines”: []}
to retry, use: --limit @/home/tidb/tidb-ansible/retry_files/deploy_ntp.retry
PLAY RECAP *********************************************************************************************************************************************
192.168.80.151 : ok=4 changed=0 unreachable=0 failed=1
192.168.80.152 : ok=4 changed=1 unreachable=0 failed=1
192.168.80.153 : ok=4 changed=1 unreachable=0 failed=1
ERROR MESSAGE SUMMARY **********************************************************************************************************************************
[192.168.80.152]: Ansible FAILED! => playbook: deploy_ntp.yml; TASK: Adjust Time | start to adjust time with 192.168.80.151; message: {“changed”: true, “cmd”: “ntpdate 192.168.80.151”, “delta”: “0:00:08.105450”, “end”: “2019-12-17 17:27:55.479743”, “msg”: “non-zero return code”, “rc”: 1, “start”: “2019-12-17 17:27:47.374293”, “stderr”: “17 Dec 17:27:55 ntpdate[5507]: no server suitable for synchronization found”, “stderr_lines”: [“17 Dec 17:27:55 ntpdate[5507]: no server suitable for synchronization found”], “stdout”: “”, “stdout_lines”: []}
[192.168.80.153]: Ansible FAILED! => playbook: deploy_ntp.yml; TASK: Adjust Time | start to adjust time with 192.168.80.151; message: {“changed”: true, “cmd”: “ntpdate 192.168.80.151”, “delta”: “0:00:08.105985”, “end”: “2019-12-17 17:27:55.512040”, “msg”: “non-zero return code”, “rc”: 1, “start”: “2019-12-17 17:27:47.406055”, “stderr”: “17 Dec 17:27:55 ntpdate[5544]: no server suitable for synchronization found”, “stderr_lines”: [“17 Dec 17:27:55 ntpdate[5544]: no server suitable for synchronization found”], “stdout”: “”, “stdout_lines”: []}
[192.168.80.151]: Ansible FAILED! => playbook: deploy_ntp.yml; TASK: Adjust Time | start to adjust time with 192.168.80.151; message: {“changed”: true, “cmd”: “ntpdate 192.168.80.151”, “delta”: “0:00:08.105045”, “end”: “2019-12-17 17:27:55.545592”, “msg”: “non-zero return code”, “rc”: 1, “start”: “2019-12-17 17:27:47.440547”, “stderr”: “17 Dec 17:27:55 ntpdate[6940]: no server suitable for synchronization found”, “stderr_lines”: [“17 Dec 17:27:55 ntpdate[6940]: no server suitable for synchronization found”], “stdout”: “”, “stdout_lines”: []}
Ask for help:
Contact us: support@pingcap.com
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. 