FAQ

Press Ctrl+Z to stop the service re-run task, and then start the service re-run task again. The displayed log shows that an error occurs in the service re-run task, as shown in the following figure.

Figure 1 task occurred error is reported during service re-run

The task is ended abnormally after executing Ctrl+Z. However, residual task process exists (and operations such as redirection and file writing are still performing), which conflict with the newly started asys re-run task. As a result, the re-run task is abnormal.

Before the asys re-run, check whether the ID of the running inference or training process exists. If yes, manually kill the process and start the asys re-run again.

When the asys tool is used to export real-time stack information, an error is reported indicating that the export times out in some scenarios. The error information is as follows:

[ASYS] [ERROR]: Generating the stackcore bin file timeout. For details, see the related description in the document.

1. The real-time stack export function has not been initialized.

   In this case, wait until the initialization is complete. You can determine that the initialization is complete based on the attr init success keyword in the plog ($HOME/ascend/log/run|debug/plog/plog-pid_*.log by default). Then, try to export the real-time stack information.

2. The ASCEND_COREDUMP_SIGNAL environment variable is set to none, and some signal sets are disabled. As a result, the real-time stack export function is unavailable.

   In this case, you can determine that the signal set is disabled based on the close the signal capture function keyword in the plog file (default path: $HOME/ascend/log/run|debug/plog/plog-pid _*.log). You need to set the ASCEND_COREDUMP_SIGNAL environment variable to enable the signal set. For details about the ASCEND_COREDUMP_SIGNAL environment variable and the signal sets for trace processing, see Environment Variables.

3. The service execution is complete, and the resources related to the real-time stack export function have been freed.

   You can determine that the resources related to the real-time stack export function have been released based on the keyword unregister all signal handlers, can not capture signal in the plog ($HOME/ascend/log/run|debug/plog/plog-pid_*.log by default). In this case, you need to execute the user service again to export the real-time stack information.

4. The real-time stack export function is abnormal.

   In this case, you can search for the keyword ERROR in the plog ($HOME/ascend/log/run|debug/plog/plog-pid_*.log by default) to view the error information and contact technical support. click here to contact technical support.