Bug ID 668522: bigd might try to read from a file descriptor that is not ready for read

Last Modified: Sep 13, 2023

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

Known Affected Versions:
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, 12.1.2, 12.1.3, 12.1.3.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3

Fixed In:
13.1.0, 13.0.1, 12.1.3.2

Opened: Jun 09, 2017

Severity: 3-Major

Symptoms

The bigd process might consume excessive CPU resources or monitor probes might be erroneously marked as failed.

Impact

The bigd process might consume excessive CPU resources for for various amounts of time. Single monitor probes might fail. Depending upon the timing of these failures, it might be possible to see monitor flapping when multiple probes for a specific monitored object happen to fail.

Conditions

External monitors are in use. External monitors include user-defined external monitors as well as built-in external monitors (for example, SNMP, LDAP, etc.).

Workaround

None.

Fix Information

An issue was resolved where the bigd process might consume excessive CPU resources or monitor probes might be erroneously marked as failed.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips