Bug ID 512634: Add logging to indicate the nitrox3 compression engine is stalled.

Last Modified: Jan 16, 2024

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

Known Affected Versions:
11.5.1 HF1, 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.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.4.1, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1

Fixed In:
13.0.0, 12.1.2, 11.6.1 HF1, 11.5.4 HF3

Opened: Mar 16, 2015

Severity: 2-Critical

Related Article: K94319023

Symptoms

The compression engine stops functioning, and new compression requests may fail. Examination of tmctl compress table shows no changes for accelerated compression, over time.

Impact

No compression; or possibly compression performed only in software (which drives up the CPU).

Conditions

Invalid request data passed into the compression engine can stall the accelerated compression engine.

Workaround

Disable accelerated compression.

Fix Information

Added detailed logging and stats to provide a clear indication that the compression engine has stalled. If hardware accelerated compression fails, compression requests are handed to the software (zlib) compression provider.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips