Bug ID 783729: Not all tcpdump process are stopped after timeout

Last Modified: Nov 15, 2019

Bug Tracker

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

Known Affected Versions:
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.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 15.0.0, 15.0.1

Opened: May 20, 2019
Severity: 4-Minor

Symptoms

tcpdump process continues to run even after timeout. Note: Tcpdump is used as part of network troubleshooting, and is not part of normal operation.

Impact

The process might be killed after the timer expires, but sometimes a tcpdump process can remain that will fill the disk if the process is not terminated manually.

Conditions

Running more than 2 tcpdump processes, for example to gather data for different VLANs at the same time.

Workaround

Explicitly terminate the process by issuing the command: tcpdump stop

Fix Information

None

Behavior Change