[
https://issues.apache.org/jira/browse/KUDU-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310039#comment-15310039
]
Todd Lipcon commented on KUDU-1475:
-----------------------------------
hm, strange that gdb isn't finding the executable. Try "gdb
/export/servers/kudu/release/kudu-tserver /path/to/core.1234"? (i.e explicitly
point at the binary in the gdb command line?) Also, glog usually prints the
stack trace of the crash somewhere below the "Check failed" message. Maybe
check the server's stdout/stderr log if you dont see it in kudu-tserver.FATAL?
> kudu-tserver restart failed due to log header not initialized.
> --------------------------------------------------------------
>
> Key: KUDU-1475
> URL: https://issues.apache.org/jira/browse/KUDU-1475
> Project: Kudu
> Issue Type: Bug
> Reporter: zhangsong
> Assignee: zhangsong
>
> when restart kudu-tserver , kudu-tserver crash due to fatal check:
> Log file created at: 2016/06/01 12:30:13
> Running on machine: BJHC-Jingo-9492.hadoop.jd.local
> Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
> F0601 12:30:13.938817 13431 log_util.h:208] Check failed:
> header_.IsInitialized()
> kudu-tserver is running in debug mode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
