Created on
05-31-2022
08:15 PM
Edited on
08-26-2024
11:09 PM
By
Jean-Philippe_P
Description |
This article describes one possible scenario when FortiGate is not updating security databases such as antivirus and Intrusion Prevention System (IPS) database. |
Scope | FortiGate. |
Solution |
Connection to FortiGuard is successful and there may not be an error in debugging of the update daemon. To check on the debug when FortiGate is updating to FortiGuard, run the following command:
diag deb app update -1 diag deb en fnsysctl killall updated exec update-now
Noticed also if the following entry in the debug log, the update of the respective databases is disabled due to a setting in FortiGate:
__update_upd_comp_by_settings[473]-Disabling FLEN components.
In conclusion, FortiGate obtains updates of security databases from FortiGuard only if the respective feature is used. If no policy is configured with the respective security profile feature, FortiGate will not download the update as the components are not in use.
If the configured policy is disabled, FortiGate will not download the update to the respective database. After enabling antivirus and/or IPS in one of the policies, run the 'execute update-now' command again. If there are no changes in the definitions, contact Technical Support for assistance or consider updating definitions manually. Refer to: Technical Tip: How to manually upgrade the IPS Engine
Related article: Technical Tip: Explanation to old update values in get system |