Log Process Startup
After the process is restarted, the newly generated logs are written into a new log file even if the size of the previous log file has not reached the limit.
Restarting the slogd Process
Restart the slogd process.
Log in to the host side server as the installation user (for example, HwHiAiUser) and run the following command:
kill slogd PID
/usr/local/Ascend/driver/tools/slogd
Restarting the log-daemon Process
Log in to the operating environment as the installation user and run the following command:
kill log-daemon PID
/usr/local/Ascend/driver/tools/log-daemon
Handling Startup Exception
If the slogd process fails to be started by using the slogd command, the two possible causes are as follows:
- Abnormal slogd.pid owner
Go to the /usr/slog directory and run the ls -l command to check whether the slogd.pid owner is the root user. If yes, delete the file and run the slogd command again to restart the slogd process.
- Disk space usage of the /var directory reaching 100%
Go to the root directory and run the df -h command. If the disk space has reached 100%, go to the /var/log/npu/slog directory and manually delete some large old log files. Run the slogd command again to restart the slogd process.