search

pingcap / tidb-ansible

Apache License 2.0
326 stars 274 forks source link

TiDB startup error #689

Open vkingnew opened 5 years ago

vkingnew commented 5 years ago

when I use ansible 2.1 to deploy TiDB 2.1.4 cluster with TiDB -binlog ,try many times to startup TiDB cluster,but it's hard to startup normal.It appears following: TASK [wait until the prometheus metrics page is available] ****************************************************************************************************************************************************************************** FAILED - RETRYING: wait until the prometheus metrics page is available (12 retries left). FAILED - RETRYING: wait until the prometheus metrics page is available (11 retries left). FAILED - RETRYING: wait until the prometheus metrics page is available (10 retries left). FAILED - RETRYING: wait until the prometheus metrics page is available (9 retries left). FAILED - RETRYING: wait until the prometheus metrics page is available (8 retries left). FAILED - RETRYING: wait until the prometheus metrics page is available (7 retries left). FAILED - RETRYING: wait until the prometheus metrics page is available (6 retries left). FAILED - RETRYING: wait until the prometheus metrics page is available (5 retries left). FAILED - RETRYING: wait until the prometheus metrics page is available (4 retries left). FAILED - RETRYING: wait until the prometheus metrics page is available (3 retries left). FAILED - RETRYING: wait until the prometheus metrics page is available (2 retries left). FAILED - RETRYING: wait until the prometheus metrics page is available (1 retries left). fatal: [172.16.4.171]: FAILED! => {"attempts": 12, "changed": false, "content": "", "msg": "Status code was -1 and not [200]: Request failed: <urlopen error [Errno 111] Connection refused>", "redirected": false, "status": -1, "url": "http://172.16.4.171:9090/metrics"} to retry, use: --limit @/home/tidb/tidb-ansible/retry_files/start.retry

OR TASK [wait until the prometheus port is up] ********************************************************************************************************************************************************************************************* fatal: [172.16.4.171]: FAILED! => {"changed": false, "elapsed": 300, "msg": "the prometheus port 9090 is not up"} to retry, use: --limit @/home/tidb/tidb-ansible/retry_files/start.retry

I'm sure the monitor hosts all port is not used by others applications.

vkingnew commented 5 years ago

when I set up parameters in inventory.ini [kafka_exporter_servers] 172.16.4.171 $$ ansible-playbook start.yml startup tidb error. because the configure file （conf/prometheus.yml）generated by ansible is error,is not knowd by promethues.

...