Technical Tip: Fix 'database not available' status

[shafiq23]

Description	This article describes how to fix the ‘database not available’ status as seen in the FortiWeb System Resources widget.
Scope	FortiWeb, FortiWeb-VM.
Solution	FortiWeb builds a database from its events, attacks, and traffic raw logs. In some cases, the database became unavailable and caused an improper log view in FortiWeb. There are also cases where the database is available but the GUI log view shows inconsistent and delayed log entries. From GUI: From CLI: Provided that this is not an issue with FortiWeb hard disks, the database status issue can be fixed by rebuilding the FortiWeb database using CLI. From CLI: Run the below CLI command for database rebuild: execute db rebuild This operation will clean and rebuild database for disklog. Do you want to continue? (y/n) Note: In v6.4.0 and earlier, database rebuild will prompt for a reboot and if machine learning is enabled, machine learning data will be lost. In v7.0 and later, FortiWeb will not reboot for database rebuild and if machine learning is enabled, machine learning data will be lost. If the problem was not resolved after executing the db rebuild, Try the following command  [A maintenance window is required as a REBOOT will be triggered]:  # execute formatlogdisk Steps to verify: From GUI: Navigate to Dashboard -> Status -> System Resources widget. Review Database Status information. From CLI: get system status If the issue persists, contact the Fortinet support team for further troubleshooting. Related article: Technical Tip: How to collect the logs needed for investigating logdisk usage and log related proble...