Skip to main content
Rajneesh
Staff
Staff
March 26, 2026

Troubleshooting Tip: FortiGate GUI becomes unresponsive when filter is applied to the logs

  • March 26, 2026
  • 0 replies
  • 396 views
Description This article describes the issue where the FortiGate GUI becomes unresponsive or gets stuck after applying filters in the Forward Logs following an upgrade to firmware v7.6.6.
Scope FortiGate.
Solution
After upgrading the FortiGate to FortiOS v7.6.6, the GUI may enter a hung or unresponsive state when applying filters on logs.
 

The issue can also be observed from the CLI using the following command:

 

diagnose sys top

 

01:44:14 PM up 4 days, 16 hours and 15 minutes
3U, 0N, 27S, 69I, 0WA, 0HI, 1SI, 0ST; 1933T, 714F
httpsd     13039 D 58.4 2.5 2 ---> (D= Disk sleep)
httpsd     13025 R 57.0 2.0 2
forticron  153   S 2.7 1.5 2
miglogd    240   S 0.5 1.6 2
node       164   S 0.3 3.1 3

 

  • The httpsd process may consume approximately 99.99% CPU usage. It can vary as well.
  • The process state may continuously change between:
    • R = Running.
    • D = Disk sleep.

 

This indicates that the GUI-related service is stuck while processing the log filter request.

 

As a workaround, disable application resolution in the GUI log display settings using the following CLI commands:
 
config log gui-display
    set resolve-apps disable
end
 
img.png

 

This issue is currently under investigation, and it is expected to be fixed in v7.6.7.