June 2026 - ripe-atlas - mailman.ripe.net

Disconnected probes
by Ernst J. Oud 06 Jun '26

06 Jun '26

The controller with a problem appears to be ctr-dub-sw01 And reg server reg03 and/or reg04. Met vriendelijke groet, Ernst J. Oud

1 0

Re: Your probe 1008669 has disconnected
by Ernst J. Oud 06 Jun '26

06 Jun '26

Yes, my three software probes that are down are on 5G connections that have a forced renew of their IP address every 24 hours. The controller in Dublin I believe has some fault. Hope RIPE corrects this asap. Met vriendelijke groet, Ernst J. Oud Met vriendelijke groet, Ernst J. Oud > On 6 Jun 2026, at 17:11, via ripe-atlas <ripe-atlas(a)ripe.net> wrote: > > Hi again, > > My number keeps going up. Looks like whenever a probe gets disconnected for some other reason, it is not able to connect back to the system. > > And my earlier count was too low already. It seems e-mail notifications aren't sent reliably. At least I didn't get one for some probes that are definitely down longer than the timeout configured (mostly default of 30 minutes). > > Cheers, > > R. > >> On 6/6/26 17:06, Ernst J. Oud wrote: >> Hi, >> Same here. Three of my software probes have disconnected this morning. Nothing wrong with internet at those locations. One of these locations also has a hardware probe that runs fine. >> In the logs it says: >> —- >> /var/atlas-probe/status/reginit.vol does not exist try new reg >> Ping failed >> start reg >> ATLAS registration starting >> there is WAIT, REG_WAIT_UNTIL , now is 1780758142 >> REG_WAIT_UNTIL expired go re-reg 1780758077 now 1780758142 >> REGHOSTS reg03.atlas.ripe.net 193.0.19.246 2001:67c:2e8:11::c100:13f6 reg04.atlas.ripe.net 193.0.19.247 2001:67c:2e8:11::c100:13f7 >> ssh -p 443 atlas@2001:67c:2e8:11::c100:13f6 INIT >> 255 REGINIT exit with error >> condmv: not moving, destination '/var/atlas-probe/data/out/v6addr.txt' exists >> condmv: not moving, destination '/var/atlas-probe/data/out/simpleping' exists >> —- >> Something definitely wrong with the controller infra! >> Regards, >> Ernst J. Oud >>>> On 6 Jun 2026, at 14:16, via ripe-atlas <ripe-atlas(a)ripe.net> wrote: >>> Hi, >>> Same thing is affecting five of my probes since yesterday, also with repeated messages of being asked to wait, or there having been an error: >>> 2026-06-06T12:13:24.673341015Z reg server asked us to wait or there was an error. REG_WAIT_UNTIL 1780748131 >>> I understand that you "updated [y]our controllers so all probes disconnected for a short while" yesterday, but that is now more than a day ago? >>> Thanks! >>> Kind regards, >>> R. >>>> On 6/6/26 00:14, Marek Küthe via ripe-atlas wrote: >>>> Hello, >>>> My probe has disconnected. Could someone take a look at this? >>>> The message in the log is as follows: >>>> ``` >>>> Jun 06 00:12:48 laplace ripe-atlas[113935]: condmv: not moving, destination '/var/spool/ripe-atlas/data/out/

1 0

Controller error?
by Ernst J. Oud 06 Jun '26

06 Jun '26

And to add insult to injury… three probes down, only one gave me a status message to that effect. So never received a notification that the other two were down too. The change to the new status email template introduced some error perhaps? Regards, Ernst J. Oud

1 0

Probe disconnect and reconnect emails with missing data
by Johan ter Beest 05 Jun '26

05 Jun '26

Hello Atlas friends, We recently changed the templates for the probe disconnect and probe reconnect messages. Unfortunately, there was a small mistake in the message parameters causing the email to appear essentially empty (no probe ID, no since, no probe description). This error has been fixed now. Apologies for the mistake, Kind regards, Johan ter Beest RIPE Atlas Team

1 0

Spam?
by Ernst J. Oud 05 Jun '26

05 Jun '26

Hi, Just received an email from atlas+e76c0ca5(a)ripe.net saying: —- Probe is disconnected () Ernst J., Your probe has been disconnected from the RIPE Atlas infrastructure since 2026-06-05 09:23:26 UTC. —- As shown above, no probe ID is mentioned and the sender’s email address is a bit weird since normal status messages come from no-reply(a)ripe.net. Also all my probes are functional. A test run at RIPE gone wrong? Regards, Ernst J. Oud

2 1