Failure Details
Important:The product name for this user guide has changed from Foundation and Cloudscape to Business Service Discovery and Migration Planning.
If any operations did not complete with a SUCCESS result code, further details on the operation are provided at the top of the report. The data is broken into sections for the Inventory and Performance colleciton processes, although some operations may be common to both components any may display twice in the report. The particular format of the data depends on the protocol in use, but generally will include the operation itself, the class of failure encountered, and any error messages or other output produced by the operation.
As an example using the SSH Collection Module, the output may be:
|
Item |
Description |
|
Reason |
Command Failure |
|
Result |
FAIL |
|
Command |
sudo ifconfig -a |
|
Exit Code |
1 |
|
Standard Output |
|
|
Standard Error |
sudo: no tty present and no askpass program specified |
In this case, the command 'sudo ifconfig -a' returned a non-zero exit status, indicating that the command did not complete successfully. As this command is critical for proper data collection, a failure from the command results in a FAIL result status, which in turn sets the Overall Status to FAIL as well. No output on the standard output stream (STDOUT) was produced, but the standard error stream (STDERR) produced the error message 'sudo: no tty present and no askpass program specified ', indicating that sudo has not been properly configured to enable the command. Further action is required, in this case to review the sudo configuration to ensure that the ifconfig command is properly permitted, according to the SSH Collection Module documentation.