Oh well, I noticed that the SOS AAAA and A statuses contained IPv6 addresses and remembered that in this CentOS VM  IPv6 had been disabled.

Restored a backup (of 2022!) of the VM and a couple of minutes later the probe registered using its IPv4 address.

But why did the VM decide last night to enable IPv6… some gremlin is living in my house. Or pure coincidence that just after the restore the controller woke up from a well earned sleep?

All alive again. Sorry to have bothered you.

Regards,

Ernst J. Oud

On 17 May 2026, at 15:42, Ernst J. Oud <ernstoud@gmail.com> wrote:



L.S.

Further to this... probe 1004467 does actually run measurements, but it apparantly can't upload the results...

There are lots of results in the Atlas data/out directory.

So the probe is running fine, but can't register.

It has a system tag of "On Hold". What does that mean?

What's up?

Regards,

Ernst


Op 17-05-2026 om 13:28 schreef Ernst J. Oud:
My software probe 1004467 disconnected from controller last ctr-dub-sw01 night. 

The CentOS VM it is running on has no problems. It has internet access. I rebooted it but that didn’t change anything.

Problem with this controller not accepting connection requests?

Other probes on this controller still work..

Regards,

Ernst J. Oud

-----
To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/