# Software probe are disconnected, will be not register. Registration servers are down?

**URL:** <https://forum.ripe.net/t/software-probe-are-disconnected-will-be-not-register-registration-servers-are-down/1587>\
**Category:** RIPE Atlas\
**Tags:** troubleshooting\
**Created:** [9 January 2026 03:08 UTC](https://forum.ripe.net/t/software-probe-are-disconnected-will-be-not-register-registration-servers-are-down/1587 "2026-01-09T03:08:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**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:** [9 January 2026 03:08 UTC](https://forum.ripe.net/t/software-probe-are-disconnected-will-be-not-register-registration-servers-are-down/1587/1 "2026-01-09T03:08:24Z")

</div>

Hello all,

For a few days now, my two software probes (#1009225 and #1009465) are no longer connected. Since then it tries to register but fails. It’s been disconnected now 24 hours.

Even removing and creating the `/etc/ripe-atlas/probe_key*` ssh key doesn’t help.

Logs:

```auto
RESULT 9011 done 1767918119 5033f079f84c ERR 255 stdout
RESULT 9011 done 1767918119 5033f079f84c stderr atlas@ctr-dub-sw02.atlas.prod.ripe.net: Permission denied (publickey).
RESULT 9011 done 1767918303 5033f079f84c ERR 255 stdout
RESULT 9011 done 1767918303 5033f079f84c stderr atlas@ctr-dub-sw02.atlas.prod.ripe.net: Permission denied (publickey).
RESULT 9011 done 1767918487 5033f079f84c ERR 255 stdout
RESULT 9011 done 1767918487 5033f079f84c stderr atlas@ctr-dub-sw02.atlas.prod.ripe.net: Permission denied (publickey).
RESULT 9011 done 1767918673 5033f079f84c ERR 255 stdout
RESULT 9011 done 1767918673 5033f079f84c stderr atlas@ctr-dub-sw02.atlas.prod.ripe.net: Permission denied (publickey).

```

and

```auto
Fri Jan 9 10:42:57 2026 daemon.err ATLAS[3700]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt' exists
Fri Jan 9 10:42:57 2026 daemon.err ATLAS[3700]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/simpleping' exists
Fri Jan 9 10:46:05 2026 daemon.err ATLAS[3700]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt' exists
Fri Jan 9 10:46:05 2026 daemon.err ATLAS[3700]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/simpleping' exists
Fri Jan 9 10:49:08 2026 daemon.err ATLAS[3700]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt' exists
Fri Jan 9 10:49:08 2026 daemon.err ATLAS[3700]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/simpleping' exists
Fri Jan 9 10:52:12 2026 daemon.err ATLAS[3700]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt' exists
Fri Jan 9 10:52:12 2026 daemon.err ATLAS[3700]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/simpleping' exists
Fri Jan 9 10:55:15 2026 daemon.err ATLAS[3700]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt' exists
Fri Jan 9 10:55:15 2026 daemon.err ATLAS[3700]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/simpleping' exists

```

Other SW probes I have are fine.

Is this a problem on my end or are the registration servers down?

Does anyone know what I could do?