You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "pizi (Jira)" <ji...@apache.org> on 2022/09/07 09:31:00 UTC
[jira] [Created] (KUDU-3398) kudu-tserver aborted when I excute src/kudu/scripts/start_kudu.sh
pizi created KUDU-3398:
--------------------------
Summary: kudu-tserver aborted when I excute src/kudu/scripts/start_kudu.sh
Key: KUDU-3398
URL: https://issues.apache.org/jira/browse/KUDU-3398
Project: Kudu
Issue Type: Bug
Components: tserver
Affects Versions: 1.16.0
Environment: os:centos8
platform：arm64
Reporter: pizi
When I finished compiling kudu， I execute src/kudu/scripts/start_kudu.sh to start t-master and t-servermin,but t-server Aborted. I have checked the ntp, and it's already synchronized.
The following error occurred：
{quote}Wrote minidump to /home/stage/root/spack-stage-kudu-1.16.0-dc5lkv24do4jdvc4xvmvuazsnctsrcyl/spack-src/tserver-2/log/minidumps/kudu-tserver/93a48256-935b-459c-f494c998-ff1863df.dmp
*** Aborted at 1662534516 (unix time) try "date -d @1662534516" if you are using GNU date ***
PC: @ 0x0 (unknown)
*** SIGSEGV (@0x2) received by PID 1136811 (TID 0xffff7e714400) from PID 2; stack trace: ***
@ 0xffff7f2205c0 ([vdso]+0x5bf)
@ 0x24802f8 _ULaarch64_is_signal_frame
@ 0x247b27c _ULaarch64_step
@ 0x239cb68 kudu::StackTrace::Collect()
@ 0x239cfa4 kudu::(anonymous namespace)::HandleStackTraceSignal()
@ 0xffff7f2205c0 ([vdso]+0x5bf)
@ 0xffff7f131f90 __GI___nanosleep
@ 0x24785a8 base::SleepForNanoseconds()
@ 0x9dc248 kudu::tserver::RunTabletServer()
@ 0x9846f4 main
@ 0xffff7e7542cc __libc_start_main
@ 0x9db730 (unknown)
{quote}
{quote}[root@localhost ~]#timedatectl
Local time: Wed 2022-09-07 17:27:02 CST
Universal time: Wed 2022-09-07 09:27:02 UTC
RTC time: Wed 2022-09-07 09:27:42
Time zone: Asia/Shanghai (CST, +0800)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
{quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)