Bug ID 501670: mcpd on secondary blades can core if the MCPD log level is set to info or debug during config sync

Last Modified: Feb 13, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
11.3.0, 11.4.0, 11.4.1

Fixed In:
11.4.1 HF9

Opened: Jan 19, 2015
Severity: 3-Major
Related AskF5 Article:
K16530

Symptoms

mcpd might core on secondary blades if the MCPD log level is set to info or debug during config sync operations.

Impact

mcpd cores, resulting in an outage or a failover.

Conditions

Perform a a config sync operations on a system with multiple blades and at least one peer, with mcpd log level set to info or debug.

Workaround

Change the MCPD log level from debug/info to notice (the default) or a higher level (so that this info-level message is not logged).

Fix Information

A log statement at the info or debug levels has been corrected so that it does not cause MCPD to crash.

Behavior Change