Bug ID 473033: Datastor Now Uses Syslog-ng

Last Modified: Nov 07, 2022

Affected Product(s):
BIG-IP AAM(all modules)

Known Affected Versions:
11.0.0, 11.1.0, 11.2.0, 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.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5

Fixed In:
12.0.0, 11.6.0 HF6, 11.5.2, 11.4.1 HF6

Opened: Jul 24, 2014

Severity: 4-Minor


Datastor did not use the normal syslog facility, causing some very rare disk full errors in /var/log.


In very rare cases, this hidden large file may cause out of disc errors, preventing logging from occurring.


When datastor is heavily overloaded or experiencing a traffic pattern that it was not designed for, it can generate copious notice messages to its log. Because datastor writes directly to its log, log rotation may seem to work, but inadvertently leave a large, hidden file in /var/log.


Log rotate can be configured to restart datastor if this becomes an issue.

Fix Information

Datastor now uses syslog-ng.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips