From b6be81f145ad0eb331b3f4e226c38e7b23d82933 Mon Sep 17 00:00:00 2001 From: foesa <35463247+foesa-yang@users.noreply.github.com> Date: Fri, 23 Dec 2022 16:37:09 +0800 Subject: [PATCH 1/3] Update 0.FAQ.md --- docs-2.0/20.appendix/0.FAQ.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs-2.0/20.appendix/0.FAQ.md b/docs-2.0/20.appendix/0.FAQ.md index 4c172e8e808..b3ebe788041 100644 --- a/docs-2.0/20.appendix/0.FAQ.md +++ b/docs-2.0/20.appendix/0.FAQ.md @@ -380,6 +380,23 @@ You also need to run [Balance Data and Balance leader](../8.service-tuning/load- Hosts with the status of `OFFLINE` will be automatically deleted after one day. +### "How do I view the dmp file?" + +The dmp file is an error report file detailing the process exit information, which can be viewed with the gdb tool that comes with the operating system. The dmp file is saved in the current directory of the startup binary(default is `/usr/local/nebula` directory) and will be generated automatically when the NebulaGraph service crashes. +1. Check the Core file process name, pid is usually a numeric value. + ``` + $ file core. + ``` +2. Use gdb to debug. + ``` + $ gdb core. + ``` +3. View the contents of the file. + ``` + $(gdb) bt + ``` +If the user is not sure about the information related to the dmp printout, you can post the printout on the [NebulaGraph Forum](https://github.com/vesoft-inc/nebula/discussions) with the operating system version, hardware configuration, error logs before and after the Core file was generated and actions that may have caused the error for help. + ## About connections ### "Which ports should be opened on the firewalls?" From a30acf0c706e0db1aef997e884df51eccf5b0001 Mon Sep 17 00:00:00 2001 From: foesa <35463247+foesa-yang@users.noreply.github.com> Date: Fri, 23 Dec 2022 17:07:21 +0800 Subject: [PATCH 2/3] Update 0.FAQ.md --- docs-2.0/20.appendix/0.FAQ.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs-2.0/20.appendix/0.FAQ.md b/docs-2.0/20.appendix/0.FAQ.md index b3ebe788041..bcae8a8331a 100644 --- a/docs-2.0/20.appendix/0.FAQ.md +++ b/docs-2.0/20.appendix/0.FAQ.md @@ -395,6 +395,19 @@ The dmp file is an error report file detailing the process exit information, whi ``` $(gdb) bt ``` +For example: +```bash +$ file core.624 +core.624: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from '/usr/local/nebula', real uid: 0, effective uid: 0, real gid: 0, effective gid: 0, execfn: '/usr/local/nebula', platform: 'x86_64' + +$ gdb /usr/local/nebula core.624 + +$(gdb) bt +... +warning: File "/usr/lib64/libthread_db-1.0.so" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load:/usr/share/gdb/auto-load". +... +``` + If the user is not sure about the information related to the dmp printout, you can post the printout on the [NebulaGraph Forum](https://github.com/vesoft-inc/nebula/discussions) with the operating system version, hardware configuration, error logs before and after the Core file was generated and actions that may have caused the error for help. ## About connections From 8a97405c2206ef3a5a6c8424fa10bf690d258c50 Mon Sep 17 00:00:00 2001 From: foesa <35463247+foesa-yang@users.noreply.github.com> Date: Fri, 23 Dec 2022 17:33:33 +0800 Subject: [PATCH 3/3] Update 0.FAQ.md --- docs-2.0/20.appendix/0.FAQ.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs-2.0/20.appendix/0.FAQ.md b/docs-2.0/20.appendix/0.FAQ.md index bcae8a8331a..5b4a678e239 100644 --- a/docs-2.0/20.appendix/0.FAQ.md +++ b/docs-2.0/20.appendix/0.FAQ.md @@ -397,14 +397,15 @@ The dmp file is an error report file detailing the process exit information, whi ``` For example: ```bash -$ file core.624 -core.624: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from '/usr/local/nebula', real uid: 0, effective uid: 0, real gid: 0, effective gid: 0, execfn: '/usr/local/nebula', platform: 'x86_64' +$ file core.1316027 +core.1316027: ELF 64-bit LSB core file, x86-64, version 1 (SYSV), SVR4-style, from '/home/workspace/fork/nebula-debug/bin/nebula-metad --flagfile /home/k', real uid: 1008, effective uid: 1008, real gid: 1008, effective gid: 1008, execfn: '/home/workspace/fork/nebula-debug/bin/nebula-metad', platform: 'x86_64' -$ gdb /usr/local/nebula core.624 +$ gdb /home/workspace/fork/nebula-debug/bin/nebula-metad core.1316027 $(gdb) bt -... -warning: File "/usr/lib64/libthread_db-1.0.so" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load:/usr/share/gdb/auto-load". +#0 0x00007f9de58fecf5 in __memcpy_ssse3_back () from /lib64/libc.so.6 +#1 0x0000000000eb2299 in void std::__cxx11::basic_string, std::allocator >::_M_construct(char*, char*, std::forward_iterator_tag) () +#2 0x0000000000ef71a7 in nebula::meta::cpp2::QueryDesc::QueryDesc(nebula::meta::cpp2::QueryDesc const&) () ... ```