jianhaiqing
commented
5 years ago login drainer machine, and try sudo systemctl start drainer-8249.service; see what happened
Open YuanDdQiao opened 5 years ago
jianhaiqing
commented
5 years ago login drainer machine, and try sudo systemctl start drainer-8249.service; see what happened
hello , sorry ,i'm comming again.
first, i gots re-deployed . but,when i deploy and start_pump ,it's no problem, and i deploy drainer it's also success,,then i get start drainer ,it's fails:
TASK [start drainer by systemd] **** ok: [mysqltest]
TASK [wait until the drainer port is up] *** fatal: [mysqltest]: FAILED! => {"changed": false, "elapsed": 300, "msg": "the drainer port 8249 is not up"} to retry, use: --limit @/home/tidb/tidb-ansible-01/retry_files/start_drainer.retry
PLAY RECAP ***** 172.19.243.118 : ok=3 changed=0 unreachable=0 failed=0 172.19.243.119 : ok=3 changed=0 unreachable=0 failed=0 172.19.243.126 : ok=3 changed=0 unreachable=0 failed=0 172.19.30.127 : ok=3 changed=0 unreachable=0 failed=0 172.19.30.128 : ok=3 changed=0 unreachable=0 failed=0 172.19.30.129 : ok=3 changed=0 unreachable=0 failed=0 172.19.30.130 : ok=3 changed=0 unreachable=0 failed=0 172.19.30.131 : ok=3 changed=0 unreachable=0 failed=0 172.19.30.132 : ok=3 changed=0 unreachable=0 failed=0 localhost : ok=1 changed=0 unreachable=0 failed=0 mysqltest : ok=4 changed=0 unreachable=0 failed=1 pump1 : ok=3 changed=0 unreachable=0 failed=0
ERROR MESSAGE SUMMARY ** [mysqltest]: Ansible FAILED! => playbook: start_drainer.yml; TASK: wait until the drainer port is up; message: {"changed": false, "elapsed": 300, "msg": "the drainer port 8249 is not up"}
Ask for help: Contact us: support@pingcap.com
it's not print log on drainer machine ,
and pump log message: ..... LevelDurations:[]} 2019/03/19 16:11:12 server.go:496: [info] writeBinlogCount: 0, alivePullerCount: 0, maxCommitTS: 407105193868787713 .....
no more other message .