Bug ID 829277: A Large /config folder can cause memory exhaustion during live-install

Last Modified: Nov 23, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP Install/Upgrade, TMOS(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, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 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

Fixed In:
16.0.0

Opened: Sep 19, 2019
Severity: 2-Critical

Symptoms

-- Live install can fail at ~96% complete. -- System memory might be exhausted, and the kernel terminates processes as a result.

Impact

The kernel terminates any number of processes; any/all critical applications might become nonfunctional.

Conditions

-- During live-install. -- Configuration roll-forward is enabled. -- The uncompressed UCS size is larger than the available memory.

Workaround

You can use these two techniques to mitigate this situation: -- Any file stored under /config is considered part of the configuration, so make sure there are no large, unnecessary files included in that directory. -- If the configuration matches or is close to total system memory size, do not roll it forward as part of live install. Instead, save the UCS manually and restore it after rebooting to the new software. To turn off config roll forward: setdb liveinstall.saveconfig disable For information about manually saving and restoring configurations, see K13132: Backing up and restoring BIG-IP configuration files with a UCS archive :: https://support.f5.com/csp/article/K13132.

Fix Information

None

Behavior Change