Bug ID 1798601: BD restart loop after upgrade on error in CONFIG_TYPE_ACCOUNT_CHARSET_TEMPLATES

Last Modified: May 08, 2025

Affected Product(s):
BIG-IP ASM, Install/Upgrade(all modules)

Known Affected Versions:
17.1.2.1

Opened: Feb 02, 2025

Severity: 2-Critical

Symptoms

After upgrade, bd goes into a restart loop. An error is logged to /var/log/bd.log: ECARD_POLICY|NOTICE|Feb 01 21:35:01.061|21460|table_funcs.cpp:1471|handle_table_dynamic CONFIG_TYPE_INTERNAL_PARAMETERS res:[0] ECARD_POLICY|NOTICE|Feb 01 21:35:01.061|21460|table_funcs.cpp:1471|handle_table_dynamic CONFIG_TYPE_ENFORCER_ACCOUNTS res:[0] ECARD_POLICY|NOTICE|Feb 01 21:35:01.063|21460|table_funcs.cpp:1471|handle_table_dynamic CONFIG_TYPE_LANGUAGE_CHARSET res:[0] ECARD_POLICY|NOTICE|Feb 01 21:35:01.067|21460|table_funcs.cpp:1471|handle_table_dynamic CONFIG_TYPE_ACCOUNT_CHARSET_TEMPLATES res:[0] BD_MISC|ERR |Feb 01 21:35:01.070|21460|temp_func.c:2296|CONFIG_TYPE_PROTOBUF_FILENAMES message had parsing error: could not parse protobuf message

Impact

BD restarts in a loop. Traffic disrupted while bd restarts.

Conditions

There is a licensing change on a device, and there is a policy that does not have any JSON profiles that have metacharElementCheck enabled.

Workaround

Run the following SQL on an affected system(s). UPDATE DCC.ACCOUNT_CHARSET_TEMPLATES AS target JOIN (SELECT policy_name_crc, charset FROM DCC.ACCOUNT_CHARSET_TEMPLATES WHERE charset_templ_id = 2) AS source ON (target.policy_name_crc = source.policy_name_crc AND target.charset = '') SET target.charset = source.charset;

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips