Hi Ernst,
I can confirm these two bugs in the behaviour of the ripe-atlas command
when waiting for the stream. In the first case, the command is
hopelessly waiting for (numProbes + 1) results, which of course never
come. In this second case, the command gives up on reading the stream
but doesn't disconnect so the process stays open.
The fixes for both of these issues are available in v3.0.3 of the
ripe-atlas-tools python package, which has just been released. Please
give this a try when you get the chance and let me know if there are any
outstanding issues.
Thanks for your mails and apologies for the inconvenience.
Regards,
Chris Amin
RIPE NCC
On 16/11/2022 19:24, Ernst J. Oud wrote:
L.S.
In the meantime I have found that there is a hardcoded 5 minute timeout for
streams to end.
However, after this timeout the message “Disconnected from stream” appears and
the ripe-atlas process appears to “hang”, a ctrl-c appears to be the only
option, python then interrupts within threading.py and client.py. What is it
doing, what is it waiting for?
Any solution?
Regards,
Ernst J. Oud
--
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas
