Compilation Successful but Startup Failed

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 编译成功启动失败

| username: yuping322

【TiDB Usage Environment】Testing, Research
【TiDB Version】master
【Encountered Problem】

/workspace/tikv/target/release (master) $ ./tikv-server --pd-endpoints=“127.0.0.1:2379” --addr=“127.0.0.1:20160” --data-dir=/tmp/tikv/data --log-file=/tmp/tikv/log/tikv.log
thread ‘main’ panicked at ‘assertion failed: cg_infos.next().is_none()’, components/tikv_util/src/sys/cgroup.rs:257:9
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
【Reproduction Path】What operations were performed to cause the problem
Compiled successfully, failed to start
【Problem Phenomenon and Impact】
/workspace/tikv/target/release (master) $ ./tikv-server --pd-endpoints=“127.0.0.1:2379” --addr=“127.0.0.1:20160” --data-dir=/tmp/tikv/data --log-file=/tmp/tikv/log/tikv.log
thread ‘main’ panicked at ‘assertion failed: cg_infos.next().is_none()’, components/tikv_util/src/sys/cgroup.rs:257:9
stack backtrace:
0: 0x5614016462b6 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hf93091c254884782
1: 0x5613ffc0c38b - core::fmt::write::hdab76e4bc2c2af88
2: 0x56140163f841 - std::io::Write::write_fmt::h5076d0a41c418267
3: 0x5614016479da - std::panicking::default_hook::{{closure}}::h82a2cb47e6cd8afd
4: 0x561401647729 - std::panicking::default_hook::h3eeadcf4f4e1229c
5: 0x561401647f2f - std::panicking::rust_panic_with_hook::h729ff4986e771f6d
6: 0x561401647de0 - std::panicking::begin_panic_handler::{{closure}}::h52afa20480ed8a8c
7: 0x561401646707 - std::sys_common::backtrace::__rust_end_short_backtrace::h7c99ed7fe73d912c
8: 0x561401647b70 - rust_begin_unwind
9: 0x5613ff7b7134 - core::panicking::panic_fmt::h368677d5ed5d9bce
10: 0x5613ff7b7018 - core::panicking::panic::h357e853061c982a7
11: 0x561401d83663 - std::sync::once::Once::call_once::{{closure}}::hf3f249e3930fefff
12: 0x5613ff81fa9c - std::sync::once::Once::call_inner::h0d402bdd337ab1fa
13: 0x561401dc1534 - tikv_util::sys::SysQuota::cpu_cores_quota::haee54025aacbf934
14: 0x561401bd3e82 - <tikv::config::TiKvConfig as core::default::Default>::default::h66cad86925514f1a
15: 0x561401d71ca7 - tikv_server::main::hc9695b6f4f29a325
16: 0x561401d5b626 - std::sys_common::backtrace::__rust_begin_short_backtrace::hdf451b70d741d968
17: 0x561401d5b63c - std::rt::lang_start::{{closure}}::h1834939c28efe4a0
18: 0x5614016390f0 - std::rt::lang_start_internal::h7034f9776301beae
19: 0x561401d7261a - main
20: 0x7f3433a3c083 - __libc_start_main
21: 0x5613ff8f0b9e - _start
22: 0x0 -
【Attachments】

Please provide the version information of each component, such as cdc/tikv, which can be obtained by executing cdc version/tikv-server --version.

| username: TiDBer_jYQINSnf | Original post link

Judging by the error, it is related to cgroup, but I don’t know the specific details.

| username: ti-tiger | Original post link

Are there any startup logs or something like that?

| username: pingyu | Original post link

It might be a bug. Could you help me file an issue?

| username: system | Original post link

This topic will be automatically closed 60 days after the last reply. No new replies are allowed.