Tiup 4.0 部署 执行报错

您好: 请查看下这里是不是有空行?

我用yaml工具看了一下,没发现空行

提供一下全量配置文件信息,不要截图,方便分析

topology .yaml (2.2 KB)

你好,

这边将配置文件粘贴至 linux 是没有问题的,看下是否粘贴有问题

我重新手动敲了一次代码,后面才可以安装。 确实存在copy的问题,哎,坑啊

你好,

:rofl: ,赞,遇到一次,以后就不会了!

为什么 start cluster集群的时候,drainer启动不了? 2020-04-13T17:29:01.404+0800 DEBUG TaskFinish {“task”: “ClusterOperate: operation=StartOperation, options={Roles:[] Nodes:[] Force:false Timeout:0}”, “error”: “failed to start: failed to start drainer: \tdrainer 172.52.1.237:8249 failed to start: timed out waiting for port 8249 to be started after 1m0s: timed out waiting for port 8249 to be started after 1m0s”, “errorVerbose”: “timed out waiting for port 8249 to be started after 1m0s\ngithub.com/pingcap-incubator/tiup-cluster/pkg/module.(*WaitFor).Execute\n\t/home/jenkins/agent/workspace/tiup-cluster-release/pkg/module/wait_for.go:89\ngithub.com/pingcap-incubator/tiup-cluster/pkg/meta.PortStarted\n\t/home/jenkins/agent/workspace/tiup-cluster-release/pkg/meta/logic.go:89\ngithub.com/pingcap-incubator/tiup-cluster/pkg/meta.(*instance).Ready\n\t/home/jenkins/agent/workspace/tiup-cluster-release/pkg/meta/logic.go:118\ngithub.com/pingcap-incubator/tiup-cluster/pkg/operation.startInstance\n\t/home/jenkins/agent/workspace/tiup-cluster-release/pkg/operation/action.go:406\ngithub.com/pingcap-incubator/tiup-cluster/pkg/operation.StartComponent.func1\n\t/home/jenkins/agent/workspace/tiup-cluster-release/pkg/operation/action.go:439\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\t/go/pkg/mod/golang.org/x/sync@v0.0.0-20190911185100-cd5d95a43a6e/errgroup/errgroup.go:57\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1357\n\tdrainer 172.52.1.237:8249 failed to start: timed out waiting for port 8249 to be started after 1m0s\nfailed to start drainer\nfailed to start”} 2020-04-13T17:29:01.404+0800 INFO Execute command finished {“code”: 1, “error”: “failed to start: failed to start drainer: \tdrainer 172.52.1.237:8249 failed to start: timed out waiting for port 8249 to be started after 1m0s: timed out waiting for port 8249 to be started after 1m0s”, “errorVerbose”: “timed out waiting for port 8249 to be started after 1m0s\ngithub.com/pingcap-incubator/tiup-cluster/pkg/module.(*WaitFor).Execute\n\t/home/jenkins/agent/workspace/tiup-cluster-release/pkg/module/wait_for.go:89\ngithub.com/pingcap-incubator/tiup-cluster/pkg/meta.PortStarted\n\t/home/jenkins/agent/workspace/tiup-cluster-release/pkg/meta/logic.go:89\ngithub.com/pingcap-incubator/tiup-cluster/pkg/meta.(*instance).Ready\n\t/home/jenkins/agent/workspace/tiup-cluster-release/pkg/meta/logic.go:118\ngithub.com/pingcap-incubator/tiup-cluster/pkg/operation.startInstance\n\t/home/jenkins/agent/workspace/tiup-cluster-release/pkg/operation/action.go:406\ngithub.com/pingcap-incubator/tiup-cluster/pkg/operation.StartComponent.func1\n\t/home/jenkins/agent/workspace/tiup-cluster-release/pkg/operation/action.go:439\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\t/go/pkg/mod/golang.org/x/sync@v0.0.0-20190911185100-cd5d95a43a6e/errgroup/errgroup.go:57\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1357\n\tdrainer 172.52.1.237:8249 failed to start: timed out waiting for port 8249 to be started after 1m0s\nfailed to start drainer\nfailed to start”}

你好,

请上传下 drainer 的报错日志看下

drainer.log (191.5 KB)

你好,

请检查使用配置中连接,是否可正常访问,创建数据库

哪个配置?不是很明白,我应该怎么检查? 我是在安装完集群,用tiup启动集群的时候报错 Starting component drainer Starting instance drainer 172.52.1.237:8249 drainer 172.52.1.237:8249 failed to start: timed out waiting for port 8249 to be started after 1m0s

Error: failed to start: failed to start drainer: drainer 172.52.1.237:8249 failed to start: timed out waiting for port 8249 to be started after 1m0s: timed out waiting for port 8249 to be started after 1m0s

Verbose debug logs has been written to /home/tidb/tiup-cluster-debug-2020-04-13-17-29-01.log. Success to stop component cluster Error: start /home/tidb/.tiup/components/cluster/v0.4.8/cluster (wd:/home/tidb/.tiup/data/Rw1tVEq) failed: exit status 1

请确定下游数据是否为以下配置,是否可正常连接,创建数据库:

这个是相当于同步节点吗?我是要在这个237的节点上先创建数据库吗?

还有一个问题,就是因为这个drainer没启动,是不是导致我后续的监控都没启动?

你好,

drainer 为 tidb binlog 组件之一,默认开启断点续传功能,需要在下游数据库创建 tidb-binlog 数据库,这个是自动的,无需手动创建

如果无法从中控机连接到该数据库,drainer 将不能正常启动。

如果对 tidb binlog 功能不太熟悉建议注释掉 dump_servers 和 drainer_servers 部分,只部署 tidb 集群部分,并将其设置为 false

binlog.enable: false

以后可以使用 tiup cluster scan-out 来部署 tidb binlog。

OK,感谢

:+1:

再请教一下,截图中红框的两个IP一定要一致吗?是否可用两个不同的IP,比如drainer是一个IP1,DB是其他IP2?