admin:debuggingcrash
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
admin:debuggingcrash [2018/10/03 17:18] – [Where to look] veera | admin:debuggingcrash [2018/10/03 18:50] (current) – [Debugging with a binary with symbols] veera | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Debugging crashes and other problems on the Trisul Probe nodes ====== | ====== Debugging crashes and other problems on the Trisul Probe nodes ====== | ||
- | Trisul probes are running on hundreds of different networks and are generally very stable. | + | Despite our best efforts with testing |
===== Where to look ===== | ===== Where to look ===== | ||
- | If you find Trisul Probe has crashed, you can collect the following information before restarting | + | If you find Trisul Probe has crashed, you can collect the following information before restarting. |
- | + | ||
- | - Trisul probe log files | + | |
- | - Version number of Trisul Probe | + | |
- | - Platform (Ubuntu/CentOS version) | + | |
- | - dmesg output | + | |
- | - Some information about the frequency of crashes | + | |
==== Log files ==== | ==== Log files ==== | ||
- | The log files on the trisul probe are stored under ''/ | + | The log files on the trisul probe are stored under ''/ |
- | + | ||
- | Another option is to use our helper | + | |
<code bash> | <code bash> | ||
+ | # add the helper aliases | ||
source / | source / | ||
- | # to change to log dir | + | # to change to probe log dir |
cd.l | cd.l | ||
- | # to tailf log file | + | # to tailf probe log file |
tailf.ns | tailf.ns | ||
+ | |||
+ | # the latest log file | ||
+ | cd.l | ||
+ | ls -lrt ns* | ||
</ | </ | ||
+ | |||
+ | When contacting Trisul Support send us the latest log file ns-xxx.log | ||
+ | |||
+ | ==== dmesg : view messages from the kernel ==== | ||
+ | |||
+ | Sometimes useful clues can be found in the kernel message log. For example, when trisul is stopped by an OOM - Out of Memory killer. | ||
+ | |||
+ | <code bash> | ||
+ | |||
+ | # to dump the kernel message log | ||
+ | dmesg -T | ||
+ | |||
+ | # to view trisul messages | ||
+ | dmesg -T | grep trisul | ||
+ | |||
+ | </ | ||
+ | |||
+ | ==== Software versions ==== | ||
+ | |||
+ | To get probe version | ||
+ | |||
+ | To get platform version '' | ||
+ | |||
+ | To get installed packages on probe | ||
+ | |||
+ | <code bash> | ||
+ | # on ubuntu | ||
+ | dpkg -l | grep trisul | ||
+ | |||
+ | # on centos | ||
+ | rpm -qa | grep trisul | ||
+ | |||
+ | </ | ||
+ | |||
+ | |||
+ | ===== Debugging with a binary with symbols ===== | ||
+ | |||
+ | If we find nothing in the Trisul and Kernel log files, we (Trisul Support) will send you a special binary image with symbols. You can then run it under '' | ||
+ | |||
+ | <note tip>We recommend you run this under the ' | ||
+ | </ | ||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | # install gdb | ||
+ | apt install gdb | ||
+ | |||
+ | # run the special trisul binary we send you like this | ||
+ | gdb --args / | ||
+ | / | ||
+ | -mode online_rxring | ||
+ | |||
+ | (...wait...) | ||
+ | |||
+ | # after it crashes - type bt on the gdb prompt | ||
+ | |||
+ | gdb: bt | ||
+ | |||
+ | ..output here.. send us this output | ||
+ | |||
+ | </ | ||
+ | |||
+ | |||
+ | |||
+ | |||
admin/debuggingcrash.1538567335.txt.gz · Last modified: 2018/10/03 17:18 by veera