admin:debuggingcrash
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
admin:debuggingcrash [2018/10/03 17:06] – created veera | admin:debuggingcrash [2018/10/03 18:09] – veera | ||
---|---|---|---|
Line 5: | Line 5: | ||
===== Where to look ===== | ===== Where to look ===== | ||
- | The following | + | If you find Trisul Probe has crashed, you can collect the following information |
- Trisul probe log files | - Trisul probe log files | ||
- Version number of Trisul Probe | - Version number of Trisul Probe | ||
Line 12: | Line 13: | ||
- Some information about the frequency of crashes | - Some information about the frequency of crashes | ||
+ | ==== Log files ==== | ||
+ | |||
+ | The log files on the trisul probe are stored under ''/ | ||
+ | |||
+ | <code bash> | ||
+ | source / | ||
+ | |||
+ | # to change to probe log dir | ||
+ | cd.l | ||
+ | |||
+ | # to tailf probe log file | ||
+ | tailf.ns | ||
+ | |||
+ | # to open the CLI | ||
+ | tp | ||
+ | |||
+ | </ | ||
+ | |||
+ | ==== 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 | ||
+ | </ | ||
admin/debuggingcrash.txt · Last modified: 2018/10/03 18:50 by veera