Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: failed to start tikv #32406

Open
20211202na opened this issue Feb 16, 2022 · 3 comments
Open

Error: failed to start tikv #32406

20211202na opened this issue Feb 16, 2022 · 3 comments
Labels
affects-5.4 This bug affects the 5.4.x(LTS) versions. affects-6.0 affects-6.1 This bug affects the 6.1.x(LTS) versions. affects-6.2 affects-6.3 affects-6.4 affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-6.6 affects-7.0 affects-7.1 This bug affects the 7.1.x(LTS) versions. affects-7.5 This bug affects the 7.5.x(LTS) versions. affects-8.1 This bug affects the 8.1.x(LTS) versions. affects-8.5 This bug affects the 8.5.x(LTS) versions. component/tikv may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. severity/major type/bug The issue is confirmed as a bug.

Comments

@20211202na
Copy link

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?

When running $ tiup cluster start tidb-test, I received an error

Starting component pd
	Starting instance node4:2379
	Starting instance node3:2379
	Starting instance node5:2379
	Start instance node5:2379 success
	Start instance node3:2379 success
	Start instance node4:2379 success
Starting component tikv
	Starting instance node8:20162
	Starting instance node6:20160
	Starting instance node7:20161

Error: failed to start tikv: failed to start: node7 tikv-20161.service, please check the instance's log(/local/tidb-deploy/tikv-20161/log) for more detail.: timed out waiting for port 20161 to be started after 2m0s

Verbose debug logs has been written to /users/nobi/.tiup/logs/tiup-cluster-debug-2022-02-16-02-18-50.log.

This is the output of $ tiup cluster display tidb-test

Screen Shot 2022-02-16 at 3 29 49 AM

And here is the error message in /local/tidb-deploy/tikv-20161/log/tikv.log:

[2022/02/16 02:23:18.076 -07:00] [WARN] [server.rs:435] ["failed to remove space holder on starting: No such file or directory (os error 2)"]
[2022/02/16 02:23:20.938 -07:00] [FATAL] [lib.rs:465] ["Failed to reserve space for recovery: Operation not supported (os error 95)."] [backtrace="   0: tikv_util::set_panic_hook::{{closure}}\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/tikv_util/src/lib.rs:464:18\n   1: std::panicking::rust_panic_with_hook\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/std/src/panicking.rs:626:17\n   2: std::panicking::begin_panic_handler::{{closure}}\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/std/src/panicking.rs:519:13\n   3: std::sys_common::backtrace::__rust_end_short_backtrace\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/std/src/sys_common/backtrace.rs:141:18\n   4: rust_begin_unwind\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/std/src/panicking.rs:515:5\n   5: std::panicking::begin_panic_fmt\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/std/src/panicking.rs:457:5\n   6: server::server::TiKVServer<ER>::init_fs::{{closure}}\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/server/src/server.rs:445:26\n   7: core::result::Result<T,E>::map_err\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/core/src/result.rs:835:27\n      server::server::TiKVServer<ER>::init_fs\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/server/src/server.rs:441:13\n      server::server::run_tikv\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/components/server/src/server.rs:155:9\n   8: tikv_server::main\n             at /home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tikv/cmd/tikv-server/src/main.rs:190:5\n   9: core::ops::function::FnOnce::call_once\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/core/src/ops/function.rs:227:5\n      std::sys_common::backtrace::__rust_begin_short_backtrace\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/std/src/sys_common/backtrace.rs:125:18\n  10: main\n  11: __libc_start_main\n             at /build/glibc-2ORdQG/glibc-2.27/csu/../csu/libc-start.c:310\n  12: <unknown>\n"] [location=components/server/src/server.rs:445] [thread_name=main]
  1. What version of TiUP are you using (tiup --version)?
    tiup version: 1.9.0
    tidb version: 5.4.0
    The cluster is set up on Emulab, and here is the config:
    https://github.com/20211202na/tidb-data/blob/main/topology.yaml
@20211202na 20211202na added the type/bug The issue is confirmed as a bug. label Feb 16, 2022
@ti-chi-bot ti-chi-bot added may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. labels Feb 16, 2022
@jebter jebter added the affects-5.4 This bug affects the 5.4.x(LTS) versions. label Feb 24, 2022
@ti-chi-bot ti-chi-bot removed the may-affects-5.4 This bug maybe affects 5.4.x versions. label Feb 24, 2022
@chengshihard
Copy link

我也碰到了这个问题 v5.4.0 请教一下 最后怎么解决的~~

@VelocityLight VelocityLight added the affects-6.1 This bug affects the 6.1.x(LTS) versions. label May 20, 2022
@tabokie
Copy link

tabokie commented May 23, 2022

Duplicate with tikv/tikv#12543. Workaround is to set tikv config storage.reserve-space to "0".

@Anutrix
Copy link

Anutrix commented May 28, 2022

Same issue is causing part of pingcap/tidb-docker-compose#111.

@VelocityLight VelocityLight added the affects-6.5 This bug affects the 6.5.x(LTS) versions. label Dec 2, 2022
@VelocityLight VelocityLight added the affects-7.1 This bug affects the 7.1.x(LTS) versions. label Apr 20, 2023
@ti-chi-bot ti-chi-bot added the affects-7.5 This bug affects the 7.5.x(LTS) versions. label Oct 23, 2023
@ti-chi-bot ti-chi-bot added the affects-8.1 This bug affects the 8.1.x(LTS) versions. label Apr 9, 2024
@ti-chi-bot ti-chi-bot added the affects-8.5 This bug affects the 8.5.x(LTS) versions. label Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-5.4 This bug affects the 5.4.x(LTS) versions. affects-6.0 affects-6.1 This bug affects the 6.1.x(LTS) versions. affects-6.2 affects-6.3 affects-6.4 affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-6.6 affects-7.0 affects-7.1 This bug affects the 7.1.x(LTS) versions. affects-7.5 This bug affects the 7.5.x(LTS) versions. affects-8.1 This bug affects the 8.1.x(LTS) versions. affects-8.5 This bug affects the 8.5.x(LTS) versions. component/tikv may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

8 participants