Re: [LTP] How to determine faults from logfile.

[William J. H. <wj...@us...>]

I believe the liner you want it something like;
      grep "stat=" ltp-logfile | grep -v "stat=0"

      Any non zero return code is in error. You would then have the name of
the testcase that's failing, and could then run this testcase individually
to determine the failure messages (probably correlating that to the code to
find out what's really going on).


Jay Huie
  wj...@us...
  zSeries Linux System Test
  Phone: 845-435-8164



"Albers, Lucas" <lu...@co...>@lists.sourceforge.net on 05/21/2002
06:40:29 PM

Sent by:    ltp...@li...


To:    "'ltp...@li...'" <ltp...@li...>
cc:
Subject:    [LTP] How to determine faults from logfile.



Hi,
I recently installed and configured the latest ltp for Linux 7.2.
I thought ltp would be useful in resolving system halts.
It have configured it to write the information to the logfile, and have
determined that there are errors in the logfile.
I am not sure how to analyze the output of the logfile and determine which
testcase caused the error?
The documentation says "that you can determine the error condition from the
logfile", but I am not sure how to do so, can someone point me in the right
direction, and perhaps update the webpage to include the 2-3 line
description of how to resolve faults from the logfile?

--Luke
Computer Science System Administrator MSU-Bozeman


Attached are the results of my lates run, which hung.

[root@morpheus tmp]# grep "stat=" /tmp/logfile | grep -v "stat=0"
tag=mprotect01 stime=1022006350 dur=0 exit=exited stat=1 core=no cu=0 cs=1
tag=msync05 stime=1022006351 dur=0 exit=exited stat=1 core=no cu=0 cs=0
tag=personality01 stime=1022006358 dur=1 exit=exited stat=1 core=no cu=0
cs=0
tag=personality02 stime=1022006359 dur=0 exit=exited stat=1 core=no cu=0
cs=0
tag=pread02 stime=1022006359 dur=0 exit=exited stat=1 core=no cu=0 cs=0
tag=recv01 stime=1022006359 dur=0 exit=exited stat=1 core=no cu=0 cs=0
tag=recvfrom01 stime=1022006359 dur=0 exit=exited stat=1 core=no cu=0 cs=1
tag=recvmsg01 stime=1022006359 dur=0 exit=exited stat=1 core=no cu=0 cs=0
tag=shmdt02 stime=1022006366 dur=0 exit=exited stat=1 core=no cu=0 cs=0
tag=mprotect01 stime=1022016548 dur=0 exit=exited stat=1 core=no cu=0 cs=0
tag=msync05 stime=1022016550 dur=0 exit=exited stat=1 core=no cu=0 cs=0
tag=personality01 stime=1022016558 dur=0 exit=exited stat=1 core=no cu=0
cs=0
tag=personality02 stime=1022016558 dur=0 exit=exited stat=1 core=no cu=0
cs=1
tag=pread02 stime=1022016558 dur=0 exit=exited stat=1 core=no cu=0 cs=0
tag=readlink04 stime=1022016558 dur=0 exit=exited stat=5 core=no cu=0 cs=2
tag=recv01 stime=1022016558 dur=0 exit=exited stat=1 core=no cu=0 cs=0
tag=recvfrom01 stime=1022016558 dur=0 exit=exited stat=1 core=no cu=0 cs=0
tag=recvmsg01 stime=1022016558 dur=0 exit=exited stat=1 core=no cu=0 cs=1
tag=shmdt02 stime=1022016565 dur=0 exit=exited stat=1 core=no cu=0 cs=0
> --Luke
> --Computer Science Sysadmin, MSU Bozeman
> --adminATcs.montana.edu 994-3931



_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

_______________________________________________
Ltp-list mailing list
Ltp...@li...
https://lists.sourceforge.net/lists/listinfo/ltp-list