Diagnose memory violation issues

From 7.2.0, you can use diagnose debug asan to collect memory violation events.

The following steps should be performed:

1. Download the symbol file which is released together with the FortiWeb image, for example: FWB_VM-64bit-v700-build0330-FORTINET.out.debug.zip.
2. Enable Debug in System > Config > Feature Visibility.
3. Upload the symbol file in System > Maintenance > Debug.
   
   After the symbol file is uploaded, you should see the following directories created on FortiWeb:
   

   /var/log/debug/symbol# ls -lh

   drwxr-xr-x 3 root 0 4.0K Apr 24 16:58 asan

   drwxr-xr-x 2 root 0 4.0K Apr 24 16:59 bin

   drwxr-xr-x 2 root 0 12.0K Apr 24 16:58 lib

   drwxr-xr-x 2 root 0 4.0K Apr 24 16:58 modules

   -rwxr-xr-x 1 root 0 170.9M Apr 24 16:58 vmlinux

   /var/log/debug/symbol#

4. Enable proxyd asan to collect memory violation events. Please note this consumes a large amount of memory thus may interfere traffic processing. Highly recommend to perform this step with the help of a Fortinet Support staff.

   diagnose debug asan proxyd enable

5. Wait for the system to collect memory violation events, and then check if the proxyd_asan.log file under /var/log/gui_upload is logged.
6. To download the proxyd_asan.log file in GUI, first enable the upload/download option in CLI:

   config system settings

   set enable-file-upload enable

   end

   You will see the proxyd_asan.log in the Backup & Restore tab in System > Maintenance > Backup & Restore. Click the Download icon to download it.
   

7. Disable proxyd asan as soon as the root cause is located, so that the memory consumed by asan proxyd can be released.

   diagnose debug asan proxyd disable