Bug ID 1240577: MCPD debug logging log.mcpd.userregex DB key does not reset to default when using 'reset-to-default'

Last Modified: Mar 12, 2025

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1

Opened: Feb 15, 2023

Severity: 4-Minor

Symptoms

The "log.mcpd.userregex" DB key is an optional filter available in MCPD debug logging that controls MCP messages logging for specific users. When this DB key is modified and then changed back to it's default value using TMSH command "reset-to-default", the previous userregex value continues to be active instead of the default value.

Impact

The previous userregex value continues to be active instead of the default value.

Conditions

- Set the MCPD debug log userregex to default using TMSH command reset-to-default. Following is an example: tmsh modify sys db log.mcpd.userregex reset-to-default

Workaround

Use the following command to set the userregex to null and in a way replicates reset-to-default option: tmsh modify sys db log.mcpd.userregex value "<null>"

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips