Logs 128T are stored in 4 principal locations:
/var/log/salt/ and in the journal.
/var/log/128technology/, as the name suggests, contains the majority of the logs related to 128T application processing.
- 128T utilizes Salt Stack for life cycle management and Dev Ops automation. Salt-related log files are contained within their default directory of
- The 128T-installer is a separate application that is used for installing and upgrading the 128T. Any logs related to installation, initialization, upgrade, or rollback will be contained within the
- The journal contains logs from processes that are managed by systemd and not by the 128T process manager. In order to view logs related to these processes, you can execute
journalctl -u <process>. 128T-related processes that are managed by systemd are:
An example listing of the
/var/log/128technology/ directory can be seen here:
You may have noticed that some log files are approximately 10MB large and others that have a
file-name.#.log format. 128T rotates logs when it starts and if a log file reaches 10MB in size. There are a maximum number of 25 rotated files per process before the oldest one gets deleted.
Each process that runs on a 128T writes to its own log. You can view the processes on your 128T by issuing the command
show system processes in the PCLI:
The log that is currently being written to is the log that does not have a number added to its name. For example, highway.log is the current highway log while highway.1.log is the most recently rotated highway log.
To rotate all your logs, issue:
Or if you want to rotate a specific process log file, issue:
To change your logging level, issue the command:
If you want to change the log level for a single process, then issue:
Log levels are:
To go back to the default log level, then issue:
You can change your default log level by configuring under your router's system settings:
To write messages to all logs:
To write messages to a certain process log:
When working with the 128T Support Team, you may be asked to bundle your logs. This is easy with the built-in 128T log compression utility:
This command bundles all the log files and other system environment properties that may be needed to diagnose issues related to 128T, and compresses them into a file in