Bug ID 1112317: Null bytes or non-ascii characters are present in velos.log

Last Modified: Jun 27, 2025

Affected Product(s):
F5OS All(all modules)

Known Affected Versions:
F5OS-A 1.0.0, F5OS-A 1.0.1, F5OS-A 1.1.0, F5OS-A 1.1.1, F5OS-A 1.2.0, F5OS-A 1.3.0, F5OS-A 1.3.1, F5OS-A 1.3.2, F5OS-A 1.4.0, F5OS-A 1.5.0, F5OS-A 1.5.1, F5OS-A 1.5.2, F5OS-A 1.5.3, F5OS-A 1.7.0, F5OS-A 1.8.0, F5OS-C 1.2.1, F5OS-C 1.2.2, F5OS-C 1.3.0, F5OS-C 1.3.1, F5OS-C 1.3.2, F5OS-C 1.5.0, F5OS-C 1.5.1, F5OS-C 1.6.0, F5OS-C 1.6.1, F5OS-C 1.6.2, F5OS-C 1.8.0, F5OS-C 1.8.1

Opened: Jun 06, 2022

Severity: 3-Major

Symptoms

Null bytes are created in the log files.

Impact

Grep considers the log file as a binary file.

Conditions

Abrupt restarts may cause this issue.

Workaround

Use ‘-a’ option in grep command.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips