Restarting Log Processes

After modifying the device-side log configuration file, restart the log processes for the modification to take effect.

After the processes are restarted, the system checks whether the previous system log file has reached its capacity limit. If it has not reached the limit, the newly generated system logs will continue to be written into the previous log file. App logs are directly written into a new log file even if the previous log file has not reached the specified capacity limit.

To restart device-side log processes, you must have the permission to log in to the device.

Ascend RC Form

Run the following command to terminate a log process (slogd, sklogd, or log-daemon):
kill -15 PID

You can run the ps -elf | grep log command to query the corresponding PID.

Run the kill -15 command to terminate the slogd process. When the slogd process receives the termination signal, the system frees the shared memory. If execution of the kill -15 command fails repeatedly, run the kill -9 command to forcibly terminate the log process.
Restart the log process.
For the Atlas 200I/500 A2 inference products, the log process automatically restarts.

After a period of time, you are advised to run the ps -elf | grep log command to check whether the restart is successful. If the restart fails: After obtaining the logs, click here to contact technical support.

Restart Exception Handling

If the log process fails to be restarted, the possible cause is that the drive space of the /var directory is overused. In this case, perform the following operations:

Go to the root directory and run the df -h command. If the drive space of the /var directory has reached 100%, delete some large old log files from the /var/log/npu/slog directory. After the deletion, start the log process.