Closed paulmenzel closed 2 years ago
Please try updating to the latest commit, and can you confirm it happens repeatedly on the same target? If it doesn't repeat, it might have been a momentarily slow/frozen reply from one of the sources queried during the trace (e.g. asname lookup for that hop IP's origin AS). Does it happen all the time, and for every target, or just this one? Any patterns that might help identifying when the slowdown happens would be useful.
I think it only happens from the Charité network, where I was connected over Eduroam.
Is there a verbose mode, so it shows exactly what is currently queried?
I added the -v
option in c95d75e to display curl targets and variables being assigned. Please try using that when launching your trace and let me know if it helps pinpointing the slowdown.
Sorry for the late response. I tried to reproduce the issue, but wasn’t able to. I am going to remember the verbose switch, should it happen again.
Today, asn hung at analyzing collected trace output.
I had to cancel it with Ctrl + c.