Bug ID 550669: Monitors stop working - throttling monitor instance probe because file descriptor limit 65436 reached

Last Modified: May 29, 2024

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

Known Affected Versions:
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.5.4 HF3, 11.5.4 HF4, 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

Fixed In:
12.1.0, 11.6.1 HF2

Opened: Oct 06, 2015

Severity: 3-Major

Related Article: K06263705


Monitor checks stop working. The ltm log file contains error messages similar to the following: 01060154:4: Bigd PID 7147, instance 0, throttling monitor instance probe because file descriptor limit 65436 reached.


Monitoring stops working; pool members are marked down when they are not.


- You have a monitor type configured that uses Tcl internally (for example, FTP, IMAP, POP3, SMTP monitors). - You have monitor logging enabled for the pool members or nodes. tmsh list ltm pool <pool_name> members { ... <member> { ... logging enabled tmsh list ltm node <node_ip> ... logging enabled


No workaround if Tcl-using monitors are configured. If pool member or node level monitor logging is configured, cease logging and restart bigd. Disable monitor logging with appropriate commands on all pools and nodes necessary: tmsh modify ltm pool <pool-name> members modify { all { logging disabled }} tmsh modify ltm node <node-ip> logging disabled Restart bigd: tmsh restart sys service bigd

Fix Information

Resolved resource leak so monitors continue to work properly.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips