Log File Descriptions
In most cases, the faults in the hardware are detected and
managed by the system (the hardware plus operating system) and not
by the test. The software and its tests are all user-level applications,
running on top of the operating system. Any error or failure that
is detected and managed by the system might not be visible to the
tests. But the occurrence of such errors or failures are logged
by the system. So, you should always check the following log files
after a run of the testing session. These log files would give a
clear picture of any error or failure that might have happened.
|
|
VTS Error File |
This file contains the failures that
are detected and reported by the VTS tests. Wherever possible, the
message includes possible causes of the error and recommended actions. |
System Log File |
These messages are reported by the syslog daemon.
They are logged in the file /var/adm/messages.
These messages are not necessarily errors, but do tell you about
any mishaps that could have occurred while tests were running. |
Output of fmdump |
Most of the errors that happen on the
system are detected, managed and reported by the system (hardware
plus operating system), using the Proactive Self Healing technology
in Oracle Solaris. Since the management of the fault happens underneath
tests, the tests themselves don't see these errors. Oracle Solaris
provides a utility called fmdump, which enables
you to display the errors and faults that the system detected (see
the man pages for fmdump for more details). After
a testing session, look at the output of the following commands
to check the errors and faults that happened during the testing
session:
fmdump -eV
fmdump |
|