BugZero found this defect 782 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
4/26/2024
BIG-IP
BIG-IP TMOS
13.1.0
13.1.0.1
13.1.0.2
13.1.0.3
13.1.0.4
13.1.0.5
13.1.0.6
13.1.0.7
13.1.0.8
13.1.1
13.1.1.2
13.1.1.3
No fixed releases provided.
Bug ID 1091021: The BIG-IP system may not take a fail-safe action when the bigd daemon becomes unresponsive. ... You may observe LTM monitors malfunctioning on your system. ... For instance, you may notice some probes are not sent out on the network, and some monitored objects are showing the wrong status. ... Impact ... -- The bigd daemon consists of multiple processes (which you can determine by running "ps aux | grep bigd"). -- One or more of the processes (but not all of them) become disrupted for some reason and stop serving heartbeats to the sod daemon. ... Under these conditions, sod will not take any fail-safe action and the affected bigd processes will continue running impaired, potentially indefinitely. ... Workaround ... If you suspect this issue is occurring in your system, you can resolve it by killing all bigd processes using the following command: pgrep -f 'bigd\.[0-9]+' | xargs kill -9 However, this does not prevent the issue from manifesting again in the future if t...