Created on
03-17-2025
11:20 PM
Edited on
06-02-2025
01:07 AM
By
Anthony_E
Description | This article describes how to troubleshoot FortiManager's failure to form an HA cluster due to ADOM corrupted. |
Scope | FortiManager. |
Solution |
diagnose debug disable diagnose debug reset diagnose debug timestamp enable diagnose debug application ha 255 diagnose debug enable
To stop the debug:
diagnose debug disable
The debug result is similar to the below:
sending file /var/ha/sync/syncsIMboD
diagnose cdb upgrade check +all
Do not select 'Y' to perform the next action, just press 'N'.
The debug result is similar to the below:
sqlite3_backup_step() failed. r1 = 11, copy /var/pm2/adom3 to /var/workspace/adom3/25162.cache, src_error = 11, dst_error = 11
Demystifying the Errors:
For more information on SQLite errors, please refer to the Result and Error Codes documentation: SQL Lite Error Code - [(11) SQLITE_CORRUPT]
After the above verification, it means adom3 (root ADOM) is corrupted. Therefore, check the command result is from FortiManager (Primary unit) or FortiManager (Secondary unit).
Go to the FortiManager unit and check the information below:
If the issue ADOM manages any devices move to another ADOM.
Use the ADOM reset CLI command to fix the issue:
execute reset adom-settings <adom> <version> <m>
For example:
execute reset adom-settings root 7 4
After that, FortiManager can form an HA cluster.
Related articles: Technical Tip: FortiManager HA cluster setup and troubleshooting Technical Tip: How to reset ADOM settings in FortiManager/FortiAnalyzer |
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.