Troubleshooting Tip: Resolving 'CMDB add entry failed' and 'CMDB command timeout' errors when saving configuration

[sharmaj]

Description	This article provides steps to perform troubleshooting when a CMDB error shows up.
Scope	FortiGate
Solution	When CMDB-related errors appear, such as 'CMDB add entry failed', and 'CMDB command timeout', it is most likely the result of the wrong upgrade path followed.  It is always recommended to follow the upgrade path according to the upgrade path tool: https://docs.fortinet.com/upgrade-tool When a user looks into the CLI by running this command: diag sys flash list Two boot partitions will be visible inside the grub configuration: active and backup. It is to be observed that the primary boot partition should have the current firmware version loaded, if not, that means the image got corrupted. Here is a solution to fix this: Try to kill the cmdb process, to do that, run the command: get sys cmdb status diagnose sys cmdb info Pay attention to the value on 'owner id'. Execute the following command: diag sys kill 11 <PID> Replace <PID> with the value of 'owner id': from the previous command. If the problem persists, the FortiGate should be rebooted. The final option is to flash format FortiGate using the guide below if the problem persists after rebooting:Formatting and loading FortiGate firmware image using TFTP  This will help to resolve the issue, if the issue persists, open the TAC ticket.