Troubleshooting Tip: FortiWeb Log Debugging Commands

[Renante_Era]

Description	This article describes the commands necessary to troubleshoot FortiWeb Log issues.
Scope	FortiWeb.
Solution	Check hard disk health. execute smart enable execute smart self-test Let the self-test run, preferably during non-business hours, as it may take several hours depending on the volume of logs. Next, run the following commands: execute smart test-result execute smart info Collect the following debug output as well in CLI diagnose policy total-conn-psec list diagnose policy total-session list diagnose policy total-traffic http list diagnose debug application logd 7 diagnose debug application oftp 7 diagnose debug enable Let the debug run for about 3 minutes before disabling debug with the following command: diagnose debug disable Open the backend shell and gather the output of the following: df -h date ls -l /var/log/fwlog/root/disklog/ ps | grep logd ps | grep indexd ps | grep mysqld cat /proc/miglog/alog/brief cat /proc/miglog/tlog/brief cat /proc/miglog/elog/brief cat /var/log/dlog_indexd cat /var/log/mysql/error.log cat /var/log/dlog_logd Wait for around 3 minutes, then re-run the above commands again. Download debug package In the GUI, enable 'Debug' under 'System Features' under System -> Config -> Feature Visibility. Go to GUI System -> Maintenance -> Debug to download the debug package.