User Tools

Site Tools


admin:debuggingcrash

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
admin:debuggingcrash [2018/10/03 17:18] – [Where to look] veeraadmin:debuggingcrash [2018/10/03 17:22] – [Log files] veera
Line 15: Line 15:
 ==== Log files ==== ==== 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. +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 :  
- +
-Another option is to use our helper aliases +
  
 <code bash> <code bash>
 source /usr/local/share/trisul-probe/trisbashrc  source /usr/local/share/trisul-probe/trisbashrc 
  
-# 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 
 +
 +# to open the CLI
 +tp
  
 </code> </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>
admin/debuggingcrash.txt · Last modified: 2018/10/03 18:50 by veera