User Tools

Site Tools


admin:debuggingcrash

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
Next revisionBoth sides next revision
admin:debuggingcrash [2018/10/03 17:06] – created veeraadmin:debuggingcrash [2018/10/03 18:09] veera
Line 5: Line 5:
 ===== Where to look ===== ===== Where to look =====
  
-The following four pieces of information will be needed :+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   - 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 ''/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>
 +
 +==== Software versions ====
 +
 +To get probe version  ''trisul --version''
 +
 +To get platform version ''uname -a'' 
 +
 +To get installed packages on probe
 +
 +<code bash>
 +# on ubuntu
 +dpkg -l | grep trisul
 +
 +# on centos
 +rpm -qa | grep trisul
  
 +</code>
  
  
  
admin/debuggingcrash.txt · Last modified: 2018/10/03 18:50 by veera