Skip to main content
Gurpreet_Kaur
Staff
Staff
January 23, 2026

Troubleshooting Tip: FortiGate disk log not showing

  • January 23, 2026
  • 0 replies
  • 1505 views
Description This article describes the steps to troubleshoot and resolve the issue of FortiGate disk logs not being displayed in the GUI. The issue is observed after updating the firewall firmware to version 7.4.9.
Scope FortiGate.
Solution

To troubleshoot the issue of FortiGate disk logs not being displayed in the GUI, follow these steps:

  • Go to Log & Report Log Settings, then select the Local Log tab.
  • Ensure that disk logging is enabled. If not, set the Disk logging toggle to Enable and select Apply to commit the change.

 

disk .png

 

Enable disk logging via the CLI:
 
config log disk setting
    set status enable
end

    

  • Run the command execute log filter reset in the CLI to clear/reset any filter settings.
  • Run the command execute log filter category 0 in the CLI to check the log filter category.
  • Run the command execute log filter device 1 in the CLI to check the log filter device.
  • Run the command execute log filter view-lines 100 in the CLI to check the log filter view lines.
  • Run the command execute log filter dump in the CLI to dump the log filter.
  • Run the command execute log display in the CLI to display the logs.
  • Run the command diagnose debug application miglogd -1 in the CLI to debug the miglogd application.
  • Run the command diagnose debug enable in the CLI to enable debug mode.
  • After 2 minutes, run the command diagnose debug disable in the CLI to disable debug mode.
  • Run the command diagnose debug reset in the CLI to reset the debug mode.
  • If the issue persists, try changing the usage of the SSD from wanopt to log by running the command config system storage in the CLI.
  • If the logs are still not showing, then in that case a process restart has to be made for the miglogd process.
  • Run the command diagnose system top 1 40 to know the status of the process and then if the process is in zombie or in dead state, then restart the process using the command fnsysctl killall miglogd.

 

Additional notes: