| Description |
This article describes how to troubleshoot when it is not possible to see logs because a 'Postgres upgrade fails' error. The issue happens when upgrading the FortiAnalyzer is a success, but the database upgrade fails. |
| Scope | FortiAnalyzer. |
| Solution |
Below are the steps to follow when encountering the issue:
exe log fortianalyzer test-connectivity
execute sql-local rebuild-db
Troubleshoot the rebuild process: diagnose test app sqllogd 4
Shows the specific log file the rebuilding process is currently handling. Must be run multiple times to track the SQL rebuild status over time.
diagnose sql show db-size
The following command checks whether the database size is increasing, indicating active rebuilding. Run this command multiple times, a few minutes apart, to confirm growth.
diagnose sql process list
Note: Refer to the following KB article for more information on the SQL rebuild process: Technical Tip: FortiAnalyzer SQL database delete and rebuild.
execute reset {all-settings | all-except-ip}
Note: This operation is irreversible: all logs, configurations, and settings will be lost.
Note: This command will erase all data on the disk, including logs, configurations, and database files |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.