Troubleshooting Log Files
The only real unique entity for logging on Cumulus Linux compared to any other Linux distribution is
switchd.log, which logs the HAL (hardware abstraction layer) from hardware.
Read this guide on NixCraft to understand how
Log File Descriptions
|Information from update-alternatives.
|Information from the
apt utility. For example, from
apt-get install and
|Information stored by the Linux audit daemon,
|Output generated by running the zero touch provisioning script (ZTP).
|Information that the system logs when the switch boots.
|Information about failed login attempts. Use the last command to view the
btmp file. For example:
cumulus@switch:~$ last -f /var/log/btmp | more
|Status of the
|Information that the system logs when you install or remove a package with the
|FRR - Used to troubleshoots routing, such as an MD5 or MTU mismatch with OSPF.
|Error and access events in Gunicorn.
|Directory containing files related to the installation of Cumulus Linux.
|Formats and prints the contents of the last login log file.
|Log file for NVUE.
|Errors and processed requests in NGINX.
|Logs for network configuration protocol.
|Prescriptive Topology Manager (PTM) errors and information.
|The HAL log for Cumulus Linux.
This is specific to Cumulus Linux. The system logs
switchd crashes here.
|The main system log, which logs everything except auth-related messages.
The primary log; grep this file to see what problem occurred.
|Login records file.