Viewing Logs (Ascend RC)

This section describes log file storage paths and main information recorded in log files in the Ascend RC form.

Logs can be aged. If logs exceed the configured storage limit, the earliest log directories or files are automatically deleted. For details about the number of log directories or files and the size of a single log file, see log configuration file.

**Table 1** Log files
Log Directory	Description
/var/log/npu/slog/debug/device-os/device-os_*.log	Debug logs generated by system processes on Ctrl CPUs, including user-mode logs and kernel-mode logs.
/var/log/npu/slog/debug/device-app-pid/device-app-pid_*.log	Debug logs generated by app processes on Ctrl CPUs.
/var/log/npu/slog/run/event/event_*.log	Event logs generated by system processes on Ctrl CPUs.
/var/log/npu/slog/run/device-os/device-os_*.log	Run logs generated by system processes on Ctrl CPUs.
/var/log/npu/slog/run/device-app-pid/device-app-pid_*.log	Run logs generated by app processes on Ctrl CPUs.
/var/log/npu/slog/security/device-os/device-os_*.log	Security logs generated by system processes on Ctrl CPUs.
/var/log/npu/slog/security/device-app-pid/device-app-pid_*.log	Security logs generated by app processes on Ctrl CPUs.
/var/log/npu/slog/debug/device-id/device-id_*.log	System logs of non-Ctrl CPUs, covering the following modules: TS TSDUMP LP
/var/log/npu/slog/slogd/slogdlog	Maintenance and debugging logs, recording the runtime status of the log tool for troubleshooting. There is an aging policy for logs. When the size of the slogdlog file reaches the specified threshold (1 MB), the file is renamed slogdlog.old for backup. The earliest backup file is deleted after each backup.
Note: Replace id and *pid* with the actual device ID and process ID, respectively. The asterisk (*) in each file name indicates the timestamp when the log file is created.