Operational Defect Database
BugZero found this defect 424 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
F5 | 1240577
MCPD debug logging log.mcpd.userregex DB key does not reset to default when using 'reset-to-default'
Last update date:
4/26/2024
Affected products:
BIG-IP
BIG-IP TMOS
Affected releases:
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
Fixed releases:
No fixed releases provided.
Description:
Bug ID 1240577: MCPD debug logging log.mcpd.userregex DB key does not reset to default when using 'reset-to-default' ... 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>"
