- ripe-atlas - mailman.ripe.net

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

software probe DNS resolving not via OS functions
by Marco Moock 21 Aug '24

21 Aug '24

Hello! I have a software probe and it does many DNS requests. I installed the nscd cache on my machine, but the probe itself doesn't use the operating system's libc functions to resolve names. Is there a special reason for that? I am aware I can install a real local caching DNS server on the machine like dnsmasq, but I would like to ask the question. :-) -- kind regards Marco

2 1

Some RIPE Atlas calls take a long time
by Ben Cartwright-Cox 20 Aug '24

20 Aug '24

Hey folks, Anyone else getting issues with some RIPE Atlas API calls taking a very long time for calls that seem like they should be simple, like a credit check? # time curl https://atlas.ripe.net/api/v2/credits/ -H 'Authorization: Key xxx-xxxx' -o /dev/null real 0m6.394s user 0m0.063s sys 0m0.005s

2 1

RIPE Atlas Infra IP Rages
by Milad Afshari 20 Aug '24

20 Aug '24

Dear Atlas Team, I hope this message finds you well. Could you please provide the exact IP range(s) used by the RIPE Atlas infrastructure? This information is crucial for our ongoing network configuration. Thank you for your assistance. Best regards, Milad

6 7

Atlas UI update 2024-08-19
by Stephen Suess 19 Aug '24

19 Aug '24

Hello Atlas community, We have just released an update to the UI that includes (among other things): - NEW: Advanced search for probes and measurement listing pages - CHANGE: Header components with new icons to match ripe.net - CHANGE: Anchors cache updated on demand (instead of 24 hours) - CHANGE: Improved debounce, reduced error messaging on measurement form If you want to see the full list of what has changed, you can check the release notes here: https://atlas.ripe.net/docs/releases/website/2024-08-19.html As always, we hope you find these changes useful and we welcome your feedback. Kind regards, Stephen Atlas UI

1 0