Hello,

These probes, along with some others, had a missing field on the server side that was preventing them connecting to the regserver. For now the issue has been resolved and they should be able to connect (I see that #1008711 is connected already), but we are looking into it further to see why it happened and to ensure it doesn't happen again.

Cheers,
Chris

On Wed, 9 Jul 2025 at 13:41, Marek Küthe <m.k@mk16.de> wrote:
Hello,

For a few hours now, my two software probes (#1008711 and #1008669) are
no longer connected. I have attached the log.

I build the software probe myself [1] and use a somewhat hardened
systemd unit [2].

Does anyone know what I could do?

Greetings
Marek Küthe

[1]
https://codeberg.org/mark22k/dn42-router/src/commit/ae9b7cc8c36a7cb0dd9ce8dd5831b9acdde0343a/roles/install-ripe-atlas/tasks/main.yml
[2]
https://codeberg.org/mark22k/dn42-router/src/commit/ae9b7cc8c36a7cb0dd9ce8dd5831b9acdde0343a/roles/config-ripe-atlas/templates/ripe-atlas.service.j2

--
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/