Bug ID 663730: Bigd prematurely kills child/external monitor process if WIFCONTINUED signal received

Last Modified: Nov 24, 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, 11.6.1 HF2, 11.6.2, 11.6.2 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, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0, 11.6.3

Opened: May 09, 2017
Severity: 3-Major

Symptoms

The bigd daemon may prematurely kill a child/external monitor process when a WIFCONTINUED signal is received for the child process.

Impact

Health monitoring using an affected monitor type may be temporarily interrupted when the child/external monitor process is killed and subsequently restarted.

Conditions

This may occur under rare timing conditions when one of the following LTM monitor types is configured and in active use: - external - ftp - imap - pop3 - snmp

Workaround

None

Fix Information

The bigd daemon now logs a message and does not prematurely kill a child/external monitor process when a WIFCONTINUED signal is received.

Behavior Change