This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Probe #1000165 showed as down in tab#status
- Previous message (by thread): [atlas] Probe #1000165 showed as down in tab#status
- Next message (by thread): [atlas] Probe #1000165 showed as down in tab#status
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Tue Mar 2 19:06:03 CET 2021
Hi,
On 2021-03-02 17:59, Jacques Lavignotte wrote:
>
>
> Le 02/03/2021 à 12:46, Viktor Naumov a écrit :
>
>> the controller's IPv6 connectivity was not restored.
>
> For post mortem analysis :
>
> Probe #1000165 is hosted by an IPV4 only machine (no IPV6)
Well, in this curious case the machine ("controller") itself thought it
*should* have IPv6, which indeed was the expected situation. Yet it
didn't. Therefore it was very confused about its own state and as a
safety measure it told its probes "hang on a minute while I figure out
my own situation" :-)
We designed the controller-probe protocol so that it can handle case
such as this; that is, the probes will try reconnecting, and in really
bad cases the system drives them to a different controller. In the
meantime they execute what they were asked and store results.
> J.
>
> Anyway : probe is ok for 5 hours, 42 minutes
Good, good!
Cheers,
Robert
- Previous message (by thread): [atlas] Probe #1000165 showed as down in tab#status
- Next message (by thread): [atlas] Probe #1000165 showed as down in tab#status
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]