Fortinet Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
alfortiuser
New Contributor

Fortimanager VM cdb check error

Hello,

We have Fortimanager(FM) VM v6.2.5 with Fortianalyzer(FAZ) enabled and it has been working fine for a quite a long time. Recently we started having all sorts of trouble with it. Disabling FAZ solves the issue with FM but we need to have FAZ. Upon doing DB checks I see the following

 

FMG-VM64 # diagnose cdb check adom-integrity
General updating - adom FortiCarrier ... An error has occured: runtime error 0: invalid value
General updating - adom xxxx... An error has occured: runtime error 0: invalid value
General updating - adom yyyy... An error has occured: runtime error 0: invalid value
General updating - adom root ... An error has occured: runtime error 0: invalid value
General updating - adom Global ... An error has occured: runtime error 0: invalid value
If the update check returns an error, please contact Fortinet Support for assistance.

 

Can't find anything online on how to fix it. Updating to v6.2.9 did not resolve the problem. Any suggestions on how to fix it?   

9 REPLIES 9
Anthony_E
Community Manager
Community Manager

Hello alfortiuser,

 

Thank you for using the Community Forum.

I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible.

 

Regards,

Anthony-Fortinet Community Team.
alfortiuser

Thank you Anthony. 

Anthony_E
Community Manager
Community Manager

Hello alfortiuser,

 

No problem at all, I am sorry you are facing such issue and I will not stop until we do not find a solution for you :)!

 

May I maybe, ask you to try the version 7 of FortiManager and FortiAnalyzer? 

It could help for fixing the issue.

 

Meanwhile, I continue to look for an answer.

 

Regards,

Anthony-Fortinet Community Team.
alfortiuser

I need to address some pending changes before I can attempt to upgrade. Some additional info. The console output returns "No space left on device". 

alfortiuser_0-1663795239439.png

 

While I am not seeing any issues via cli

Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                 4037400    374168   3663232   9% /
none                   4037412         0   4037412   0% /dev
none                   7507456         0   7507456   0% /dev/shm
none                     65536        20     65516   0% /tmp
/dev/sda1               503752    139392    364360  28% /data
/dev/mdvg/mdlv       397902844  26365104 371521356   7% /var
/dev/mdvg/mdlv       397902844  26365104 371521356   7% /drive0
/dev/mdvg/mdlv       397902844  26365104 371521356   7% /Storage
/dev/loop0                8887        97      8278   1% /var/dm/tcl-root

 

FMG-VM64 #
FMG-VM64 #
FMG-VM64 #
FMG-VM64 # execute lvm info
LVM Status: OK
LVM size: 380GB

 

Disk1 :         Used       80GB
Disk2 :         Used      300GB

Anthony_E
Community Manager
Community Manager

Hello,

 

Thank you fo these informations.

I will help to find a solution.

 

Regards,

Anthony-Fortinet Community Team.
Anthony_E
Community Manager
Community Manager

Hi!

 

So a FortiManager expert told me to process like that:

 

" This needs further troubleshooting

we need to open a second ssh and execute the following command


# di de app securityconsole 255
# di de en

 

In any case, he is inviting you to open a ticket if needed.

 

Regards,

 

 

 

Anthony-Fortinet Community Team.
alfortiuser

Thank you. Running these commands return no output with and without FAZ enabled. And I am not able to open a ticket on FMG.

At this point we do not care about FAZ data. Can i just reinstall FMG and do restore from backup. Any special instructions?

Anthony_E
Community Manager
Community Manager

Hello,

 

Ok, I will then come back to him and give you his answer.

 

Regards,

Anthony-Fortinet Community Team.
Anthony_E
Community Manager
Community Manager

Hello alfortiuser,

 

I had an answer :):

 

"yes it is possible to perform a backup of the config or a snapshot on your vm and then re-install the backup or the snapshot."

 

Hope it will help :)!

 

Regards,

Anthony-Fortinet Community Team.