Subject: I didnt understand why is RIPE Atlas probe are not working properly.
Relevant details:
- Cold reboot for couple of times and then again, still ctr-dub-sw01.
- Power cycle couple of times → no luck
- Reinstalled entire disk drive→ still no luck
- Private key permissions: -rw------- (600) → confirmed correct
- I’ve confirmed the public key in /etc/ripe-atlas/probe_key.pub matches exactly what’s registered on the portal for this probe, and I’ve re-saved the key on the portal multiple times to force a re-sync, but the issue persists.
- No /var/atlas-probe/status/ssh_err.txt file present
- Logs shows repeated
condmv: not movingresult, each failing quickly (not timing out) with a clean handshake completes quickly.
condmv: not moving, destination '/probe/var/spool/ripe-atlas/data/out/v6addr.txt' exists
condmv: not moving, destination '/probe/var/spool/ripe-atlas/data/out/simpleping' exists
condmv: not moving, destination '/probe/var/spool/ripe-atlas/data/out/v6addr.txt' exists
condmv: not moving, destination '/probe/var/spool/ripe-atlas/data/out/simpleping' exists
condmv: not moving, destination '/probe/var/spool/ripe-atlas/data/out/v6addr.txt' exists
condmv: not moving, destination '/probe/var/spool/ripe-atlas/data/out/simpleping' exists
It’s my log. I`m using OpenWrt 25.12, Docker host.
This repeats every 3 minutes, always with the same condmv: not moving result. Since the SSH handshake completes quickly (not a timeout/network issue) and the key is confirmed to match on both ends, this looks like the ctr-dub-sw01 isn’t recognizing the probe even though the portal shows it as connected but it does not send any measurements data.
What should I do to see if there’s something wrong with my setup?
Could someone from RIPE NCC take a look at probe list on the backend below:
- Probe ID 1009000
- Probe ID 1013973
- Probe ID 1015467
- Probe ID 1015468
Happy to provide any further logs or the exact public key fingerprint if useful.
Thanks in advance!