RIPE NCC Atlas probes are going offline: `controller INIT exit with error`
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#G9caVaD8bxLiDvSmHF4HEsZAEjMrW7Gchvj... / https://paste.burble.com/?cecb8def804b373d#GyNsT22QBmii4PGZFnRnVP6mLQC9vhsvj... [4] https://i.ping.pe/o/L/img_oL3R8bjI.png [5] https://codeberg.org/mark22k/dn42-router/src/commit/5c855adbbca45263268ba5dc... I would appreciate an answer! -- Marek Küthe m.k@mk16.de er/ihm he/him
I believe this is more widespread. Probe 1005072 always connects to controller ctr-hel09 but it now tries to connect to ctr-dub-sw01 and fails. Please advice. Regards, Ernst J. Oud
On 21 Aug 2024, at 22:40, Marek Küthe <m.k@mk16.de> wrote:
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#G9caVaD8bxLiDvSmHF4HEsZAEjMrW7Gchvj... / https://paste.burble.com/?cecb8def804b373d#GyNsT22QBmii4PGZFnRnVP6mLQC9vhsvj... [4] https://i.ping.pe/o/L/img_oL3R8bjI.png [5] https://codeberg.org/mark22k/dn42-router/src/commit/5c855adbbca45263268ba5dc...
I would appreciate an answer!
-- Marek Küthe m.k@mk16.de er/ihm he/him ----- 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/
Hello Marek, It seems we are having some issues with the controllers at the moment, this may be the root cause of the problem. Please be aware though, the current status of the debian package is still very much in development as noted in the INSTALL and README. It may not work perfectly yet. Next release will include full Debian support. Regards, Michel
On 21 Aug 2024, at 22:40, Marek Küthe <m.k@mk16.de> wrote:
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#G9caVaD8bxLiDvSmHF4HEsZAEjMrW7Gchvj... / https://paste.burble.com/?cecb8def804b373d#GyNsT22QBmii4PGZFnRnVP6mLQC9vhsvj... [4] https://i.ping.pe/o/L/img_oL3R8bjI.png [5] https://codeberg.org/mark22k/dn42-router/src/commit/5c855adbbca45263268ba5dc...
I would appreciate an answer!
-- Marek Küthe m.k@mk16.de er/ihm he/him ----- 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/
participants (3)
-
Ernst J. Oud -
Marek Küthe -
Michel Stam