Closed adrianlzt closed 3 years ago
If skydive is restarted, and its using ES as backend, that {}
value in Metadata.TCPConn/TCPListen is parsed correctly and does not produce a panic.
Looks like it was only happening if TCPListen/TCPConn was defined at node creation time with the API.
Has been fixed (no more panics, just warning message) in 2d4a0e33d1f0c1b2acd4f2b11f2789124ce6122f (proccon: check network info has the expected format)
If Metadata.TCPConn/TCPListen is empty (
{}
), the garbage collector panics.Steps to reproduce:
Wait till next GC:
proccon should not panic, but return a warning message.
This could be reached if some node sends some connection data, the GC delete all network info in the first pass and panics in the second pass.