Description
This article describes the grab-log-snapshot report as one utility that collects a snapshot of a system's logfiles, stacktrace and memory information plus other information needed in order to diagnose a problem.
Logs should be collected during any of the following scenarios:
- Reproducing a problem (additional debug may need to be enabled. Use the commands provided by Support or in the applicable integration reference manual in the Document Library).
- The appliance is hung for some reason.
- Something about an 'OutOfMemory' issue is seen on the appliance.
- Slow performance of the appliance/VM is noticed.
- The 'processes are down' message appears on the GUI instead of the login.
Important:
- The utility has to be run prior to a reboot of the appliance. In some instances, a reboot can destroy evidence of a problem.
- If a Control Server/Application Server or a High Availability pair is in use, the script has to be run on each appliance.
Scope
Version: FortiNAC legacy 8.x and greater.
Version: FortiNAC-OS 7.2.x and greater.
Solution
GUI Instructions (available in versions 9.4, 7.2, and greater):
This will generate and download a snapshot of the logs directly from the browser. The status is shown at the bottom right of the screen.
In HA environment when Primary is in control, there is a possibility to generate secondary node grab-log-snapshot from GUI.
Click on ? Question Mark icon, then into the "Gear" (settings) icon:
Download logs - Advanced option to download primary or/and secondary node grab-log-snapshot will appear:
Click on the image to view it in greater detail.
CLI Instructions (CentOS appliance):
- Log into the CLI of the appliance as root.
- Execute the script:
grab-log-snapshot
The script will collect and zip a large number of files.
This will take several minutes.
The resulting zip file (log-snapshot-<hostname>-<timestamp>.tar.gz) is located in the /tmp directory.
For example:
grab-log-snapshot
This program grabs a snapshot of the system logfiles.
It takes several minutes to run.
Gathering logfiles...
Gathering system info....
Grabbing stacktraces....
Grabbing memory info....
Grabbing scheduler info....
Grabbing cluster network info....
Grabbing license info...
Packaging logfiles (takes a little while)...
All done.
Prelink messages that state that 'at least one of file's dependencies has changed since prelinking' can be ignored.
Logs are here: /tmp/log-snapshot-fortinac.forti.lab-20230428160858.tar.gz
Give this file to Support.
If a CPU performance or a memory-usage are experienced the problem, arrange with Support to run the collect-linux-debug-info script.
- Retrieve the grab-log-snapshot file(s) to submit to Support. This can be done using WinSCP or a similar application (specify SCP protocol) to download the files from the appliance.
- Submit to Support. Open a support ticket and upload the files. Note: A comment must be added in order for the file to be saved.
If the file(s) are too big, contact Support for assistance.
