Last Modified: Feb 13, 2019
See more info
Known Affected Versions:
11.3.0, 11.4.0, 11.4.1
Opened: Jan 19, 2015
Related AskF5 Article: K16530
mcpd might core on secondary blades if the MCPD log level is set to info or debug during config sync operations.
mcpd cores, resulting in an outage or a failover.
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.
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).
A log statement at the info or debug levels has been corrected so that it does not cause MCPD to crash.