Bug ID 618517: bigd may falsely complain of a file descriptor leak when it cannot open its debug log file; bigd stops monitoring

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2

Fixed In:
13.0.0, 12.1.2 HF1, 11.6.1 HF2

Opened: Sep 23, 2016
Severity: 3-Major
Related AskF5 Article:
K61255401

Symptoms

- In v11.6.1, bigd reports pool members were marked down that are not actually down, and logs messages similar to the following in the ltm log file: warning bigd[7413]: 01060154:4: Bigd PID 7413 throttling monitor instance probe because file descriptor limit 65436 reached. - Because of changes in the v12.1.x software, although the problem is still present, it has negligible impact.

Impact

- On v11.6.1 this can cause bigd to stop monitoring, resulting in pool members being marked down erroneously. - In v12.1.x, some of the underlying logging code changed, and there is no real impact.

Conditions

-- Monitoring is in use. -- bigd debug logging is enabled. -- The bigd debug log file (/var/log/bigdlog) is full.

Workaround

Prevent the log file from getting full. To do so, rotate the log file using the following command: logrotate -f bigdlog

Fix Information

Stopped bigd from thinking it was out of file descriptors when it was unable to open its debug log file.

Behavior Change