Trisul Network Analytics
Developer Zone

**This is an old revision of the document!** ----

====== Debugging crashes and other problems on the Trisul Probe nodes ====== Trisul probes are running on hundreds of different networks and are generally very stable. We also put them though fuzz tests and mangled packets to test the stability. However, it is possible that sometimes the Probes stop. This document describes how you can debug such events. ===== Where to look ===== If you find Trisul Probe has crashed, you can collect the following information before restarting and see if you find some clues. - Trisul probe log files - Version number of Trisul Probe - Platform (Ubuntu/CentOS version) - dmesg output - Some information about the frequency of crashes ==== Log files ==== The log files on the trisul probe are stored under ''/usr/local/var/log/trisul-probe/domain0/probe0/context0'' The latest ''ns-xxx.log'' contains the most recent logs before the crash. You can also use the helper bash aliases : <code bash> source /usr/local/share/trisul-probe/trisbashrc # to change to probe log dir cd.l # to tailf probe log file tailf.ns # to open the CLI tp </code> ==== 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. To view dmesg output <code bash> # to dump the kernel message log dmesg -T # to view trisul messages dmesg -T | grep trisul </code>