I just upgraded my FortiAnalyzer to 7.6.2 from 7.6.1 and ran into an issue where all devices in all adoms were showing as Not Connected or logging.
The local FortiGate devices would show the fabric connected and no queued logs. Sniffers also showed good bi-directional communication.
Had to run “diagnose system fsck harddisk” on the FortiAnalyzer, which repaired the file system and rebooted the FortiAnalyzer. Now all devices are logging correctly.
Wanted to possibly save someone some headache if they also ran into this issue!
Hi edison65,
Additional, if the FSCK does not fix the issue, please rebuild the DB of FAZ. The command will be #execute sql-local rebuild-db <---It requires a restart.
Before run rebuild DB, need to ensure the FAZ still receiving a log and insert to the archive.
diag fortilogd status >> should be running
diag fortilogd lograte-device >> should show the FGT receiving log and should show number. ( If 0.00 FAZ not receiving a log )
diag fortilogd lograte-type >> volume of log FGT sending
User | Count |
---|---|
2101 | |
1185 | |
770 | |
451 | |
344 |
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.