Troubleshooting Process
This document provides self-service fault locating and troubleshooting methods based on various fault symptoms that developers may encounter during inference and training, helping developers quickly locate and rectify faults. The content includes error code information printed on the screen and troubleshooting methods, one-click log collection, and usage of various fault locating tools.
The troubleshooting process includes collecting the fault information, analyzing the fault cause, and rectifying the fault. Figure 1 shows the troubleshooting process.
- Collecting the fault information
Collect fault information as it is critical to troubleshooting. The information includes but is not limited to logs and environment information.
Log information can be analyzed using the top-to-bottom log analysis method typically. Fault symptoms are narrowed down to the bottom layer based on the service process.
For details about log levels, log paths, and log files, see Log Reference.
- Analyzing the fault cause
Find possible causes of the fault and locate its root cause by using certain methods or measures.
- Recording the troubleshooting process
Record key information about the troubleshooting process, and provide preventive measures and workarounds to avoid similar faults.
You can also share your troubleshooting cases with other developers on Developer Forum.
The third-party tools (such as eseye u and Netron) involved in the troubleshooting process provided in this document are only examples. You can replace them with other similar tools to meet your actual requirements.