Bug ID 1053741: Bigd may exit and restart abnormally without logging a reason

Last Modified: May 29, 2024

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

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,,,, 17.0.0,,

Fixed In:
17.1.0, 16.1.4, 15.1.8

Opened: Oct 08, 2021

Severity: 3-Major


Certain fatal errors may cause the bigd daemon to exit abnormally and restart to recover. For many such fatal errors, bigd logs a message in the LTM log (/var/log/ltm) indicating the fatal error that occurred. For some causes, no message is logged to indicate what error occurred to cause big to exit abnormally and restart


It may be difficult to diagnose the reason that caused bigd to exit abnormally and restart.


This may occur when bigd encounters a fatal error when monitoring LTM pool members, particularly (although not exclusively) when using In-TMM monitor functionality (sys db bigd.tmm = enable).


To enable logging of all fatal errors that cause bigd to exit abnormally and restart, enable bigd debug logging: tmsh modify sys db bigd.debug value enable With bigd debug logging enabled, bigd messages (including such fatal errors) will be logged to /var/log/bigdlog

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips