Skip to main content
llombardi
Staff
Staff
November 4, 2025

Troubleshooting Tip: Config error log 'cache-mem-percent' post upgrade from v7.2 to v7.4 in FortiGate

Description

This article describes the reason why the following config error log post upgrade to v7.4 in FortiGate could be faced:

 

diagnose debug config-error-log read
>>> "set" "cache-mem-percent" "1" @ global.webfilter.fortiguard:command parse error (error -61)

Scope FortiGate.
Solution

The message 'set cache-mem-percent 1 @ global.webfilter.fortiguard:command parse error (error -61)' is a parse error due to a change in the configuration parameter from 'cache-mem-percent' in v7.2 to 'cache-mem-permille' in v7.4.

 

  • In v7.0/7.2, under 'config webfilter fortiguard', the default configuration is:

 

config webfilter fortiguard

    set cache-mem-percent 2

 

  • In v7.4, the same configuration has the following default value:

 

config webfilter fortiguard

    set cache-mem-permille 1

 

  • To check the current value, run the following command on the system (in Global if multi VDOM mode is enabled):

 

show full-configuration webfilter fortiguard | grep cache-mem

 

The change was made to allocate a minor portion of memory for the rating cache, which was considered more justified.
The default value was changed from 2% (set cache-mem-percent 2) to 0.1% (set cache-mem-permille 1) of the FortiGate memory.

Thought Leadership. Security Summit. Thursday, November 12th, PGA National Resort, Palm Beach Gardens, FL.
Thought Leadership. Security Summit. Thursday, October 8th. Disney's Grand Californian Hotel & SPA, Anaheim, CA.
Security Operations Summit: Modernize SecOps. Operate AI-Native.AMER: November 4 | 9:00 AM PST. India and SAARC: November 5 | 10:00 AM IST. EMEA: November 5 | 10:30 AM CET. APAC: November 5 | 11:00 AM SGT