# Probe 1007887 cant register again

**URL:** <https://forum.ripe.net/t/probe-1007887-cant-register-again/1218>\
**Category:** RIPE Atlas\
**Created:** [12 November 2024 21:06 UTC](https://forum.ripe.net/t/probe-1007887-cant-register-again/1218 "2024-11-12T21:06:08Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tschaefer](https://avatars.discourse-cdn.com/v4/letter/t/a9a28c/32.png) [@tschaefer](https://forum.ripe.net/u/tschaefer)\
**Post date:** [12 November 2024 21:06 UTC](https://forum.ripe.net/t/probe-1007887-cant-register-again/1218/1 "2024-11-12T21:06:08Z")

</div>

```auto
Nov 12 20:56:15 atlas11 ripe-atlas[8530]: 255 REGINIT exit with error
Nov 12 21:02:24 atlas11 ripe-atlas[8598]: 255 REGINIT exit with error
Nov 12 21:08:32 atlas11 ripe-atlas[8667]: 255 REGINIT exit with error
Nov 12 21:27:02 atlas11 ripe-atlas[8875]: 255 REGINIT exit with error
Nov 12 21:39:21 atlas11 ripe-atlas[9010]: 255 REGINIT exit with error
Nov 12 21:42:24 atlas11 ripe-atlas[9047]: 255 REGINIT exit with error
Nov 12 21:48:33 atlas11 ripe-atlas[9116]: 255 REGINIT exit with error
Nov 12 21:51:36 atlas11 ripe-atlas[9187]: 255 REGINIT exit with error
Nov 12 21:57:45 atlas11 ripe-atlas[9615]: 255 REGINIT exit with error

```

and

```auto
Nov 12 22:03:05 atlas11 perd[818]: USER root pid 0 cmd condmv -A "RESULT 9901 ongoing" /home/atlas/data/new/main /home/atlas/data/out/main
Nov 12 22:03:50 atlas11 ripe-atlas[769]: RESULT 9006 done 1731445430 d83add97e970 no reginit.vol start registration
Nov 12 22:03:50 atlas11 ripe-atlas[769]: /run/ripe-atlas/status/reginit.vol does not exist try new reg
Nov 12 22:03:53 atlas11 ripe-atlas[769]: Ping works
Nov 12 22:03:53 atlas11 ripe-atlas[769]: start reg
Nov 12 22:03:53 atlas11 ripe-atlas[9687]: ATLAS registration starting
Nov 12 22:03:54 atlas11 ripe-atlas[9687]: there is WAIT, REG_WAIT_UNTIL , now is 1731445434
Nov 12 22:03:54 atlas11 ripe-atlas[9687]: REG_WAIT_UNTIL expired go re-reg 1731445370 now 1731445434
Nov 12 22:03:54 atlas11 ripe-atlas[9687]: REGHOSTS reg03.atlas.ripe.net 193.0.19.246 2001:67c:2e8:11::c100:13f6 reg04.atlas.ripe.net 193.0.19.247 2001:67c:2e8:11::c100:13f7
Nov 12 22:03:54 atlas11 ripe-atlas[9687]: ssh -p 443 atlas@2001:67c:2e8:11::c100:13f7 INIT
Nov 12 22:03:55 atlas11 ripe-atlas[9687]: reg server asked us to wait or there was an error. REG_WAIT_UNTIL 1731445551
Nov 12 22:03:55 atlas11 ripe-atlas[9706]: condmv: not moving, destination '/var/spool/ripe-atlas/data/out/v6addr.txt' exists
Nov 12 22:03:55 atlas11 ripe-atlas[9707]: condmv: not moving, destination '/var/spool/ripe-atlas/data/out/simpleping' exists

```

---

<div class="post-metadata">

**Author:** ![mtheofy](https://avatars.discourse-cdn.com/v4/letter/m/ac91a4/32.png) [@mtheofy](https://forum.ripe.net/u/mtheofy)\
**Post date:** [12 November 2024 23:51 UTC](https://forum.ripe.net/t/probe-1007887-cant-register-again/1218/2 "2024-11-12T23:51:30Z")

</div>

Getting similar problems for probe 1001231 after ISP reassigned an IPv4 and IPv6 prefix (probably CPE reboot). The probe fails to register

---

<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:** [13 November 2024 01:38 UTC](https://forum.ripe.net/t/probe-1007887-cant-register-again/1218/3 "2024-11-13T01:38:53Z")

</div>

Same here (SW probe [1008601](https://atlas.ripe.net/probes/1008601)). After a disconnect for a few hours on the VM in the network side, the probe is no longer connecting.

Log:

```auto
Wed Nov 13 00:59:25 2024 local6.err eperd[8776]: root: No such file or directory
Wed Nov 13 01:01:18 2024 daemon.err ATLAS[8677]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt' exists
Wed Nov 13 01:01:18 2024 daemon.err ATLAS[8677]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/simpleping' exists
Wed Nov 13 01:03:28 2024 daemon.warn odhcpd[1516]: No default route present, overriding ra_lifetime!
Wed Nov 13 01:04:26 2024 daemon.err ATLAS[8677]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt' exists
Wed Nov 13 01:04:26 2024 daemon.err ATLAS[8677]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/simpleping' exists
Wed Nov 13 01:07:37 2024 daemon.err ATLAS[8677]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt' exists
Wed Nov 13 01:07:37 2024 daemon.err ATLAS[8677]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/simpleping' exists
Wed Nov 13 01:10:03 2024 daemon.warn odhcpd[1516]: No default route present, overriding ra_lifetime!
Wed Nov 13 01:10:48 2024 daemon.err ATLAS[8677]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt' exists
Wed Nov 13 01:10:48 2024 daemon.err ATLAS[8677]: condmv: not moving, destination '/usr/libexec/atlas-probe-scripts/data/out/simpleping' exists

```

Running the command manually i get:

```auto
ssh -p 443 atlas@ctr-dub-sw01.atlas.prod.ripe.net
The authenticity of host '[ctr-dub-sw01.atlas.prod.ripe.net]:443 ([54.77.167.52]:443)' can't be established.
RSA key fingerprint is (redacted).
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])? (redacted)
Warning: Permanently added '[ctr-dub-sw01.atlas.prod.ripe.net]:443' (RSA) to the list of known hosts.
atlas@ctr-dub-sw01.atlas.prod.ripe.net: Permission denied (publickey).

ping ctr-dub-sw01.atlas.prod.ripe.net

Pinging ctr-dub-sw01.atlas.prod.ripe.net [54.77.167.52] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 54.77.167.52:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

```

As always, SOS packets are still being sent even though it says it’s disconnected:

 ![p1008601_sos](https://europe1.discourse-cdn.com/flex013/uploads/ripe/original/1X/6d30c780e861f92023d2403b7b77374653f4751d.png)

---

<div class="post-metadata">

**Author:** ![mixtery](https://avatars.discourse-cdn.com/v4/letter/m/47e85d/32.png) [@mixtery](https://forum.ripe.net/u/mixtery)\
**Post date:** [13 November 2024 02:14 UTC](https://forum.ripe.net/t/probe-1007887-cant-register-again/1218/4 "2024-11-13T02:14:27Z")

</div>

Same at [id 1002930](https://atlas.ripe.net/probes/1002930). Tried upgrade from 5080 to 5100 but nothing.

---

<div class="post-metadata">

**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:** [13 November 2024 09:15 UTC](https://forum.ripe.net/t/probe-1007887-cant-register-again/1218/5 "2024-11-13T09:15:21Z")

</div>

Indeed there’s a problem right now, we have an entry on our status page: [https://status.ripe.net/](https://status.ripe.net/)

---

<div class="post-metadata">

**Author:** ![mixtery](https://avatars.discourse-cdn.com/v4/letter/m/47e85d/32.png) [@mixtery](https://forum.ripe.net/u/mixtery)\
**Post date:** [13 November 2024 15:35 UTC](https://forum.ripe.net/t/probe-1007887-cant-register-again/1218/6 "2024-11-13T15:35:33Z")

</div>

Already resolved, connected almost for 6 hours, thanks.
