Technical Tip: Tracing errors when editing objects from GUI
Description
Sometimes problems occur when editing, creating or deleting objects through the graphic interface (GUI). The object might be referenced, or you might not be able to edit at all.
This article explains how to debug issues related to the graphical interface of the FortiGate.
Solution
Check also how the behaviour is with the CLI equivalent of change that the user is trying to accomplish.
To disable debugging run the following commands:
Sometimes problems occur when editing, creating or deleting objects through the graphic interface (GUI). The object might be referenced, or you might not be able to edit at all.
This article explains how to debug issues related to the graphical interface of the FortiGate.
Solution
Open two SSH sessions.
1) Gathering system related debugs.
get system status <---- Gathering status and logs from the system to be studied.get system performance statusdiag sys top 1 40 <----- Run for 30 seconds and press CTRL + C to stop.diag hardware sysinfo shmdiag debug crashlog readdiag sys top-mem 20diag sys top-summary '-s mem' <----- Keep running until the end, this is to monitor the behavior of processes when the problem is reproduced.Note: top-summary is not available in 6.4 anymore
2) Enable the following debugs:
Replicate the issue afterwards via GUI and attach the debugs to the support ticket.diag debug resetdiag debug console timestamp enablediag debug application httpsd -1diag debug cli 8diag debug cmdb-trace 1diag debug enable
Check also how the behaviour is with the CLI equivalent of change that the user is trying to accomplish.
To disable debugging run the following commands:
diag debug cli 0
diag debug disable
diag debug reset