wcnspect does not clean up the previous pktmon capture

Open daschott opened this issue 3 years ago • 0 comments

Describe the bug Sometimes, the wcnspect server does not clean up a previous pktmon capture, leaving behind a running pktmon instance. Despite this, future captures still work since wcnspect will terminate any idle captures when attempting to start a new capture.

Component: Server

To Reproduce wcnspect capture -t "tcp_SYN" -i "my_ip" all

Expected behavior I expect the server to clean up the output

Windows OS Version (please complete the following information):

Server 2022 (20348.1006)

Orchestrator and Version (e.g. Kubernetes v1.24, ContainerD v1.6.8):

containerD 1.6.6, K8s v1.23

Anything else we need to know?: You can issue a pktmon stop on any of the nodes to clean up any actively running pktmon instances manually.

The actively running capture does not take up disk space since the pktmon capture is executed in interactive mode only (output to stdout).

Sep 20 '22 17:09 daschott