Bug ID 965897: Disruption of mcpd with a segmentation fault during config sync

Last Modified: Jul 27, 2021

Bug Tracker

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

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0

Opened: Nov 19, 2020
Severity: 2-Critical

Symptoms

The mcpd process on the peer device fails with a segfault, restarts and then segfaults again in a loop Numerous messages may be logged in the "daemon" logfile of the following type: emerg logger[2020]: Re-starting mcpd

Impact

Continuous restarts of mcpd process on the peer device.

Conditions

-- High availability (HA) configuration -- A port-and-address list configuration is changed to be only an address list -- A config sync occurs

Workaround

One possible measure for getting the peer-machine "mcpd" out of its failure mode is to command the still-functioning system to push a "full" config sync to the appropriate device group. Doing this twice consecutively may be necessary. # tmsh run /cm config-sync force-full-load-push to-group APPROPRIATE-DEVICE-GROUP

Fix Information

None

Behavior Change