Bug #5172
closed
Napatech stream mismanagement following non-transient error
Added by Jeff Lucovsky almost 3 years ago.
Updated 9 months ago.
Label:
Needs backport to 6.0
Description
When a non-transient error, such as a "time merge error" occurs in the Napatech packet loop, the stream on which the error occurred is never closed. A new stream is opened, however.
Following a non-transient error from NT_NetRxGet
, the stream should be closed with NT_NetRxClose
before a new stream is opened.
Because the original stream is not closed, it'll fill up and then 100% packet loss follows.
A simple time change -- as shown below -- is enough to trigger the hard error
import subprocess
import time
shift = 0
print(f"Shifting time by {shift} seconds")
print("Current", time.time())
replacement = int(time.time()) + shift
expected = time.time() + 10
subprocess.check_call(["date"])
subprocess.check_call(["date", "-s", f"@{replacement}"])
- Assignee changed from OISF Dev to Phil Young
- Label deleted (
Needs backport to 5.0)
- Target version changed from 7.0.0-beta1 to TBD
- Status changed from New to In Review
- Assignee changed from Phil Young to Jeff Lucovsky
- Status changed from In Review to Closed
Also available in: Atom
PDF