- ripe-atlas - mailman.ripe.net

Probe v3 id #22785 - BADMD-APP
by Cassiano Aquino 26 Aug '24

26 Aug '24

Hi, I have a probe with id #22785 that completed 10 years online last July, but today in the morning it stopped working. I tried the common procedure, remove the USB, which was the same the probe came with, never had major issues with it, restart, wait 10 minutes, put the USB drive back again. Usually this solved any problems I had in the past, but not today, after trying 4 different USB drives, I'm seeing the same error message on the SOS log: BADMD-APP-5080-d41d8cd98f00b204e9800998ecf8427e Is there anything else I can do? Considering that after ten years, this probe is almost part of the family, is there any hope to recover? I have another TP-LINK TL-MR3020 that I bought and almost never used, is it possible somehow to install the firmware on it to have it replacing the current probe? Thanks in advance, and I do understand if there is nothing we can do, but probe #22785, you will be missed! Cheers, Cassiano Aquino - EI5HPB

3 3

Fwd: Your RIPE Atlas Probe (ID: 60200) has reconnected
by Ernst J. Oud 25 Aug '24

25 Aug '24

> We're just letting you know that your probe (#60200 ) has re-established its link to our network and we are again receiving data from it. Good! After over 3 days. Connected to controller ctr-nue17. Not to ctr-dub anymore. Ernst

2 1

Probe v3, problems
by Phillip Remaker 24 Aug '24

24 Aug '24

I tried to replace by failing v2 probe with a v3 probe I had mailed to me from a closed site https://atlas.ripe.net/probes/16058/' The first led is on, second is off, and 3rd is slow-blink, which indicates a "network problem"? I tried a different power supply, replaced the network cable, tried other ports and even put in a new power supply, all with no change. The DHCP server does not see it. Any other suggestions?

1 1

Disconnected #27262
by Victor TALVAZ 24 Aug '24

24 Aug '24

Hi everyone, It seems that I've been totally disconnected for 2 hours, 8 minutes, is the controller ctrl-dub-hw01 alive ? Probe #27262. Thanks, Regards, *Victor TALVAZ*

3 2

Another probe disconnected
by Ernst J. Oud 23 Aug '24

23 Aug '24

Hi, And just now probe 1004467 also has been disconnected. What is going on? Regards, Ernst J. Oud

6 9

Re: Auto reconnect?
by Ernst J. Oud 23 Aug '24

23 Aug '24

Ok. Hope so. But it is weird that probes try to connect to a controller that clearly is not responding. I have six probes, 5 work fine, 1 is now disconnected for 34 hours. If it would connect to the controller it always used to connect to - ctr-nue14- all would be well but it appears it persists to connect to a non functioning controller, probably ctr-dub-hw01. Or something else is going awry in fail over between controllers perhaps? I know this is a free non-critical service but the lack of communication here wonders me a bit. Especially since the downtime is longer than ever before. Ernst > On 23 Aug 2024, at 17:56, Nick Hilliard (INEX) <nick(a)inex.ie> wrote: > > Ernst J. Oud wrote on 23/08/2024 16:54: >> Do we need to take actions to have disconnected probes reconnect “over the weekend”? Or is a reconnect in this case automatically? > probes automatically reconnect, as far as I'm aware. > > Nick

1 0

Auto reconnect?
by Ernst J. Oud 23 Aug '24

23 Aug '24

I asked before but this list appears to be not for support questions? Try again… Do we need to take actions to have disconnected probes reconnect “over the weekend”? Or is a reconnect in this case automatically? Regards, Ernst J. Oud

1 0

RIPE NCC Atlas probes are going offline: `controller INIT exit with error`
by Marek Küthe 22 Aug '24

22 Aug '24

Hello, I am running two RIPE NCC Atlas Probes [1] [2] and both went offline a few hours after each other and a `controller INIT exit with error` appears in the log [3]. What can I do about this? The controller also seems to be somehow not pingable [4]. I use Debian 12 with the self-compiled .deb package (version 5090) and use a slightly hardened systemd unit [5]. [1] https://atlas.ripe.net/probes/1008669/ [2] https://atlas.ripe.net/probes/1008711/ [3] https://paste.i2pd.xyz/?2c936299e0b7473f#G9caVaD8bxLiDvSmHF4HEsZAEjMrW7Gchv… / https://paste.burble.com/?cecb8def804b373d#GyNsT22QBmii4PGZFnRnVP6mLQC9vhsv… [4] https://i.ping.pe/o/L/img_oL3R8bjI.png [5] https://codeberg.org/mark22k/dn42-router/src/commit/5c855adbbca45263268ba5d… I would appreciate an answer! -- Marek Küthe m.k(a)mk16.de er/ihm he/him

3 2

Also probe 60200 is disconnected (4G-T-Mobile)
by Ernst J. Oud 22 Aug '24

22 Aug '24

Hi, Yesterday (SW) probe 1005072 disconnected and this morning (HW) probe 60200 disconnected. This also happened on July 18th with exactly these same two probes, then it apparently was a problem in the Atlas infra. Please advice. Regards, Ernst J. Oud Begin forwarded message: > From: RIPE Atlas <no-reply(a)ripe.net> > Date: 22 August 2024 at 08:30:02 CEST > To: ernstoud(a)euronet.nl > Subject: Probe 60200 is disconnected (4G-T-Mobile) > Reply-To: RIPE Atlas <no-reply(a)ripe.net> > > Dear Ernst J. Oud, > > Your probe 60200 has been disconnected from the RIPE Atlas infrastructure since 2024-08-22 05:52:00 UTC. > > You may be able to learn more about the possible cause from the "Status" tab on your probe's information page: > > https://atlas.ripe.net/probes/60200/#!tab-status > > Probes are tagged with suspected problems every four hours, so if there is nothing listed under the Status tab and your probe has just gone offline, please check back in a few hours, as more information may be available. > > If you need further assistance or have any questions, please contact us at atlas(a)ripe.net. > > Kind regards, > > RIPE Atlas Team > > ********** > This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to be notified if your probe becomes disconnected for more than 30 minutes. If you want to change this, or disable this notification altogether, please go to https://atlas.ripe.net/probes/60200/, and click the "edit" button under "Notifications".

1 0

RIPE NCC Atlas probes are going offline: `controller INIT exit with error`
by Marek Küthe 21 Aug '24

21 Aug '24

Hello, I am running two RIPE NCC Atlas Probes [1] [2] and both went offline a few hours after each other and a `controller INIT exit with error` appears in the log. What can I do about this? The controller also seems to be somehow not pingable [3]. I use Debian 12 with the self-compiled .deb package (version 5090) and use a slightly hardened systemd unit [4]. [1] https://atlas.ripe.net/probes/1008669/ [2] https://atlas.ripe.net/probes/1008711/ [3] https://i.ping.pe/o/L/img_oL3R8bjI.png [4] https://codeberg.org/mark22k/dn42-router/src/commit/5c855adbbca45263268ba5d… I would appreciate an answer! -- Marek Küthe m.k(a)mk16.de er/ihm he/him

1 0