Verify whether the issue is present across different web browsers. Clear the browser cache and cookies, then attempt to access the affected GUI page again.
The following image shows an example where the GUI page remains loading without displaying information:
 If the issue persists, restart the WAD process responsible for GUI management.
First, check the system utilization (CPU/RAM) via the CLI:
erbium-kvm10 # get system performance status
CPU states: 0% user 0% system 0% nice 100% idle 0% iowait 0% irq 0% softirq
CPU0 states: 0% user 0% system 0% nice 100% idle 0% iowait 0% irq 0% softirq
CPU1 states: 0% user 0% system 0% nice 100% idle 0% iowait 0% irq 0% softirq
Memory: 4034996k total, 986664k used (24.5%), 2528252k free (62.7%), 520080k freeable (12.8%)
Average network usage: 813 / 604 kbps in 1 minute, 355 / 153 kbps in 10 minutes, 254 / 52 kbps in 30 minutes
Maximal network usage: 11911 / 11146 kbps in 1 minute, 11911 / 11146 kbps in 10 minutes, 11911 / 11
Note that restarting the wad process has the below impact:
Run the following command:
fnsysctl killall wad
If the issue persists after restarting the WAD process, collect debug logs while reproducing the issue on the affected GUI page.
Run the following commands:
diagnose wad debug enable category http
diagnose wad debug enable category gui-api
diagnose debug application httpsd -1
diagnose debug enable
After reproducing the issue, stop the debug process:
diagnose debug disable
diagnose debug reset
Reproduce the issue, export the debug output into a .txt file, and open a support case with Fortinet Technical Assistance Center for further analysis: Technical Tip: Ticket Creation via the Support Portal.
|