Bug ID 617382: Csyncd memory leak on multi-bladed systems

Last Modified: Nov 12, 2019

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1

Fixed In:
13.0.0, 12.1.5

Opened: Sep 18, 2016
Severity: 3-Major

Symptoms

Csyncd memory use increases over time. It may fail due to large size (>2 to 3 GB), possibly leading to this ltm log: err csyncd[8258]: 013b0004:3: Fatal error: fork failed. Memory pressure may develop, leading to an increased use of swap, and the system may become sluggish and show other low-memory symptoms. If memory pressure is severe, the Linux oom killer will likely terminate csyncd. On systems with more free memory, csyncd will terminate with a core file when it is approaching 4GB in size. In both cases csyncd automatically restarts.

Impact

Low free memory may lead to system instability. If memory pressure is severe, the Linux oom killer will likely terminate csyncd. On systems with more free memory, csyncd will terminate with a core file when it is above ~2.2 GB in size. In both cases csyncd automatically restarts.

Conditions

Multi-bladed vCMP guest or VIPRION.

Workaround

Restart csycnd on all blades to free the memory it has in use: clsh bigstart restart csyncd This is typically not service-affecting.

Fix Information

Memory leak identified and fixed.

Behavior Change