Description
This article describes how to rectify the issue when failing to create ADOM in FortiAnalyzer/FortiManager.
Note:
FortiManager with the FortiAnalyzer feature enabled will have this issue.
Scope
FortiManager, FortiAnalyzer.
Solution
Make sure the Allocated storage has not reached to Maximum Available inside the Disk Utilization, by right it will automatically max out the value.
Give about 20-30% less than the Maximum Available storage to successfully create the ADOM.
For debugging, this can be seen in FortiManager, where the commands are:
diag debug service dvmdb 255
diag debug enable
Will see an example of logs that caused it to fail to create the ADOM:
Request [gui webworker:15700:1]:
{ "client": "gui webworker:15700", "id": 1, "method": "add", "params": [{ "current_adom": 3, "data": { "create_time": 0, "desc": "", "flags": 2056, "lock_override": 0, "log_db_retention_hours": 1440, "log_disk_quota": 24479, "log_disk_quota_alert_thres": 90, "log_disk_quota_split_ratio": 70, "log_file_retention_hours": 8760, "mig_mr": 0, "mig_os_ver": 0, "mode": 1, "mr": 4, "name": "faf", "os_ver": 7, "primary_dns_ip4": "0.0.0.0", "primary_dns_ip6_1": 0, "primary_dns_ip6_2": 0, "primary_dns_ip6_3": 0, "primary_dns_ip6_4": 0, "restricted_prds": 1, "secondary_dns_ip4": "0.0.0.0", "secondary_dns_ip6_1": 0, "secondary_dns_ip6_2": 0, "secondary_dns_ip6_3": 0, "secondary_dns_ip6_4": 0, "state": 1, "tz": -1, "uuid": "", "workspace_mode": 0}, "target start": 1, "url": "adom"}], "root": "dvmdb", "session": 63149}
Chkperm Response [gui webworker:15700:1]:
{ "id": 1, "result": [{ "status": { "code": 0, "message": "OK"}, "url": "adom"}], "session": 63149}
Response [gui webworker:15700:1]:
{ "id": 1, "result": [{ "status": { "code": -20019, "message": "Out of range"}, "url": "adom"}]}
If the Storage of the ADOM was not an issue, run the below command in FortiManager/FortiAnalyzer CLI to repair the File system:
diagnose system fsck harddisk
