Bug ID 437025: big3d might exit during loading of large configs or when a connection to mcpd is dropped.

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2

Fixed In:
11.6.0, 11.5.4, 11.4.1 HF2, 11.3.0 HF9, 11.2.1 HF11

Opened: Nov 07, 2013
Severity: 2-Critical
Related Article:
K15698

Symptoms

If big3d loses its connection to MCPD and cannot reconnect immediately, big3d retries too often and re-uses timer IDs incorrectly. This might result in a core dump with either SIGABRT or SIGSEV. One way this can happen is that while processing very large configs, the mcpd process does not respond to queries from the big3d process.

Impact

big3d core errors.

Conditions

A large configuration file (for example, larger than 10 MB) or a very busy MCPD/control plane.

Workaround

This issue has no workaround at this time.

Fix Information

Very large configuration files (for example, larger than 10 MB) or a very busy MCPD/control plane no longer causes big3d core errors.

Behavior Change