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.

Sign up for GitHub

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

Jump to bottom

Update 0.FAQ.md #1824

Merged
merged 3 commits into from
Dec 23, 2022
Merged

Update 0.FAQ.md #1824

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b6be81f
Update 0.FAQ.md
foesa-yang Dec 23, 2022
a30acf0
Update 0.FAQ.md
foesa-yang Dec 23, 2022
8a97405
Update 0.FAQ.md
foesa-yang Dec 23, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 31 additions & 0 deletions docs-2.0/20.appendix/0.FAQ.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -380,6 +380,37 @@ 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.<pid>
foesa-yang marked this conversation as resolved.
Show resolved Hide resolved
```
2. Use gdb to debug.
```
$ gdb <process.name> core.<pid>
```
3. View the contents of the file.
```
$(gdb) bt
```
For example:
```bash
$ 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 /home/workspace/fork/nebula-debug/bin/nebula-metad core.1316027

$(gdb) bt
#0 0x00007f9de58fecf5 in __memcpy_ssse3_back () from /lib64/libc.so.6
#1 0x0000000000eb2299 in void std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_construct<char*>(char*, char*, std::forward_iterator_tag) ()
#2 0x0000000000ef71a7 in nebula::meta::cpp2::QueryDesc::QueryDesc(nebula::meta::cpp2::QueryDesc const&) ()
...
```

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?"
Expand Down