Technical Tip: Tracing errors when editing objects from GUI

[sagha]

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

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 status 

diag sys top 1 40                   <----- Run for 30 seconds and press CTRL + C to stop.

diag hardware sysinfo shm 

diag debug crashlog read

diag sys top-mem 20

diag 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:

diag debug reset

diag debug console timestamp enable

diag debug application httpsd -1 

diag debug cli 8

diag debug cmdb-trace 1

diag debug enable

Replicate the issue afterwards via GUI and attach the debugs to the support ticket.
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