Bug ID 746704: Syslog-ng Memory Leak

Last Modified: Oct 16, 2019

Bug Tracker

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

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1

Fixed In:
15.0.0

Opened: Oct 12, 2018
Severity: 3-Major

Symptoms

After a long uptime (almost a year) syslog-ng had consumed 1.1G of virtual memory on BIG-IP.

Impact

Minimal. This is a leak of virtual memory. If syslog-ng does not read or write to this memory it will not be consume physical memory.

Conditions

Memory leak when syslog-ng handles continuous SIGHUP signals.

Workaround

Run this command once a month: service syslog-ng restart

Fix Information

None

Behavior Change