# Software probe won't reconnect after being disconnected for 2 weeks **URL:** \ **Category:** RIPE Atlas\ **Tags:** troubleshooting\ **Created:** [25 August 2025 08:25 UTC](https://forum.ripe.net/t/software-probe-wont-reconnect-after-being-disconnected-for-2-weeks/1528 "2025-08-25T08:25:09Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![dot](https://avatars.discourse-cdn.com/v4/letter/d/dc4da7/32.png) [@dot](https://forum.ripe.net/u/dot)\ **Post date:** [25 August 2025 08:25 UTC](https://forum.ripe.net/t/software-probe-wont-reconnect-after-being-disconnected-for-2-weeks/1528/1 "2025-08-25T08:25:09Z")
Hi there, I’m posting this on behalf of a (currently unavailable) friend whose software probe 1008470 won’t reconnect after being down for 2 weeks (this was a planned maintenance on his side). The logs look like this: ripe-atlas-1 | /run/ripe-atlas/status/reginit.vol does not exist try new reg ripe-atlas-1 | Ping works ripe-atlas-1 | start reg ripe-atlas-1 | ATLAS registration starting ripe-atlas-1 | REREG\_TIMER 1754726353 expired now is 1756105940 ripe-atlas-1 | REREG\_TIMER\_EXPIRED go re register REREG\_TIMER 1 , now is 1756105940 ripe-atlas-1 | REGHOSTS [reg03.atlas.ripe.net](http://reg03.atlas.ripe.net) 193.0.19.246 2001:67c:2e8:11::c100:13f6 [reg04.atlas.ripe.net](http://reg04.atlas.ripe.net) 193.0.19.247 2001:67c:2e8:11::c100:13f7 ripe-atlas-1 | ssh -p 443 atlas@2001:67c:2e8:11::c100:13f6 INIT ripe-atlas-1 | 255 REGINIT exit with error ripe-atlas-1 | condmv: not moving, destination ‘/var/spool/ripe-atlas/data/out/v6addr.txt’ exists ripe-atlas-1 | condmv: not moving, destination ‘/var/spool/ripe-atlas/data/out/simpleping’ exists even changing the /etc/ripe-atlas/probe\_key\* ssh key doesn’t help. Does any of you know a way around it? Cheers Denis ---
**Author:** ![pyg](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.ripe.net/pyg/32/750_2.png) [@pyg](https://forum.ripe.net/u/pyg)\ **Post date:** [25 August 2025 19:58 UTC](https://forum.ripe.net/t/software-probe-wont-reconnect-after-being-disconnected-for-2-weeks/1528/2 "2025-08-25T19:58:27Z")
Hi, Thanks @dot for the post. I went a bit further with my troubleshooting. It looks like my probe key has not been deployed on all Ripe’s target servers. The server which refused my key this morning, now accepts it. ```auto ssh -vv -p 443 -i /etc/ripe-atlas/probe_key -T atlas@2001:67c:2e8:11::c100:13f6 INIT 2>&1 | grep "accepts" debug1: Server accepts key: /etc/ripe-atlas/probe_key RSA SHA256:Fq6dAwH/PiDJtCWYh/EklbuiCti6vCTTyhykcqCvcjc explicit ``` But my probe now tries to connect to `193.0.19.25`which refuses the connection. ```auto ssh -vv -p 443 -i /etc/ripe-atlas/probe_key -T atlas@193.0.19.25 INIT atlas@193.0.19.25: Permission denied (publickey). ``` Greetings, Pierre-Yves ---
**Author:** ![robertk](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.ripe.net/robertk/32/413_2.png) [@robertk](https://forum.ripe.net/u/robertk)\ **Post date:** [1 September 2025 14:07 UTC](https://forum.ripe.net/t/software-probe-wont-reconnect-after-being-disconnected-for-2-weeks/1528/3 "2025-09-01T14:07:10Z")
Hello, the most likely cause is that the probe is using a different key than what’s on record. As the host you can change / update this for SW probes in the UI. If this doesn’t help then can you share your probe id? It’s best to do this in a ticket to [atlas@ripe.net](mailto:atlas@ripe.net) with the pub.key included so we can check. ---
**Author:** ![pyg](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.ripe.net/pyg/32/750_2.png) [@pyg](https://forum.ripe.net/u/pyg)\ **Post date:** [3 September 2025 13:13 UTC](https://forum.ripe.net/t/software-probe-wont-reconnect-after-being-disconnected-for-2-weeks/1528/4 "2025-09-03T13:13:10Z")
Hello, I have tried several times to delete the two files `/etc/ripe-atlas/probe_key*`and upload the freshly re-generated pub file on [RIPE Atlas - RIPE Network Coordination Centre](https://atlas.ripe.net/probes/1008470/manage) (using the “Update SSH key” feature) ; the probe kept reporting `255 REGINIT exit with error` messages. Will create a ticket then. ---
**Author:** ![ph\_ybarro](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.ripe.net/ph_ybarro/32/872_2.png) [@ph\_ybarro](https://forum.ripe.net/u/ph_ybarro)\ **Post date:** [8 January 2026 02:06 UTC](https://forum.ripe.net/t/software-probe-wont-reconnect-after-being-disconnected-for-2-weeks/1528/5 "2026-01-08T02:06:23Z")
I went a extensive troubleshooting. It’s yet another issue with the controller [ctr-dub-sw01/2 btw]. It’s been disconnected now for 12 hours as it gives useful listing a ton of SOS messages as well. It’s trying to register to `reg03 ctr-dub-sw02` and `reg04 ctr-dub-sw02`. Even removing and creating the `/etc/ripe-atlas/probe_key*` ssh key doesn’t help, the probe kept reporting `255 controller INIT exit with error` and `atlas@ctr-dub-sw02.atlas.prod.ripe.net: Permission denied (publickey)` messages, The logs look like this: > Thu Jan 8 09:31:41 2026 daemon.err ATLAS[3700]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt’ exists > Thu Jan 8 09:31:41 2026 daemon.err ATLAS[3700]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/simpleping’ exists > Thu Jan 8 09:34:45 2026 daemon.err ATLAS[3700]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt’ exists > Thu Jan 8 09:34:45 2026 daemon.err ATLAS[3700]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/simpleping’ exists > Thu Jan 8 09:37:48 2026 daemon.err ATLAS[3700]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt’ exists > Thu Jan 8 09:37:48 2026 daemon.err ATLAS[3700]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/simpleping’ exists [Probe 1009225](https://atlas.ripe.net/probes/1009225/overview) and [1009465](https://atlas.ripe.net/probes/1009465/overview) Other SW probes I have are fine. The problems are with the Atlas registration servers or infrastructure in general. Is there a special problem with sw-probes? ---
**Author:** ![robertk](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.ripe.net/robertk/32/413_2.png) [@robertk](https://forum.ripe.net/u/robertk)\ **Post date:** [21 January 2026 13:52 UTC](https://forum.ripe.net/t/software-probe-wont-reconnect-after-being-disconnected-for-2-weeks/1528/6 "2026-01-21T13:52:59Z")
Hello, we have thousands of software probes, many of them come and go regularly, so I can state that the infra is working as intended. I’d believe the problem is either local (firewalls?) or your probes and our infra disagree on what keys are used. We can follow-up (if we haven’t already) in a support ticket,