Troubleshooting Tip: Restart logd process to restore of showing logs in GUI for FortiWeb

[adavila]

Description	This article describes how to solve the issue of showing the logs in a FortiWeb despite these being enabled (System, Traffic, and Attack logs). This problem is associated with the process 'logd' which stops showing new logs in the GUI console. The behavior is documented in bug 870313, but the procedure to restart the process works in any situation, associated with logs.
Scope	FortiWeb v7.x.
Solution	Identify the 'ID process number' for the 'logd' process by running the command: diagnose system top | grep logd The 'Process ID number' will be the first number in the line where the process was found. See this example: 23366 1 root S 243m 0.7 1 0.0 /bin/logd The 'Process ID number' (Process_ID) for this example is 23366. Kill (restart) the logd process by running  the command: diagnose system kill 9 <Process_ID> In the example used, the command will be: diagnose system kill 9 23366 Note: This method also helps to solve CPU, Memory, and GUI errors. So if CPU and memory sometimes get stuck and show a high percentage, killing processes for them will help to solve the issue. Instead of a logd process, just filter processes related to memory, CPU, or GUI(httpsd) and kill them.