Troubleshooting Updater

FDS Authorization Failed

Go to the System > FortiGuard.

If the following databases show FDS Authorization Failed, that means the FortiNDR unit is using a Fortiguard License that does not include FortiNDR entitlements (for example, a machine that was upgraded from FortiAI v1.5.3 GA to FortiNDR v7.0 GA).

Although some functions will still work, important new features in v7.0 such as web filtering cannot be used and any NDR-related databases cannot be downloaded. Please contact sales for information about updating the existing FortiGuard support license.

For other FDS Authorization Failed errors, this is most likely due to an expired FortiGuard support license or a network configuration problem such as a DNS setting that is directing the updater to the wrong FDS servers.

Clearing updater cache files

Normally, after triggering an update through the CLI with exec update now or through the GUI with the Update FortiGuard Neural Network Engine button, the status will change to Downloading or Installing:

Sometimes an update will not go through due to failed FDS connection during a download and the cache will need to be cleared.

Running the command and then try updating again:

exec update clean-up

Thius should solve that problem. Rebooting the machine will also trigger a FDS download cache-cleanup operation upon startup.

Diagnosing Other FDS Errors

To further diagnose updating errors, please run the CLI commands:

diagnose debug application updated DEBUG_LEVEL

diagnose debug enable

A DEBUG_LEVEL is a bit mask consisting of 3 bits.

• A DEBUG_LEVEL of 1 will show only the error. Usually a DEBUG_LEVEL of 1 is enough to pinpoint the problem.
• A DEBUG_LEVEL of 3 will show all major events and errors.
• A DEBUG_LEVEL of 7 will show all events and errors.