Failed reporting, http return code 302 on ctr-dub-sw01.atlas.prod.ripe.net

RIPE Atlas
1

Hi,

I set up a probe yesterday using the jamesits/ripe-atlas docker container, and it has connected ok, but I am still not seeing any results. Checking logs, I see repeated instances of

httppost: before getaddrinfo
httppost: before connect
httppost: sending request
posting file '/var/spool/ripe-atlas/data/out/ooq/1'
posting file '/var/spool/ripe-atlas/data/out/ooq/2'
posting file '/var/spool/ripe-atlas/data/out/ooq/3'
posting file '/var/spool/ripe-atlas/data/out/ooq/4'
posting file '/var/spool/ripe-atlas/data/out/ooq/5'
posting file '/var/spool/ripe-atlas/data/out/ooq/6'
posting file '/var/spool/ripe-atlas/data/out/ooq/7'
posting file '/var/spool/ripe-atlas/data/out/ooq/8'
posting file '/var/spool/ripe-atlas/data/out/ooq/9'
posting file '/var/spool/ripe-atlas/data/out/ooq/0'
httppost: getting result
httppost: POST command failed: '302 Found'
httppost: leaving with error
ooqd: httppost failed with 1

It connects to ctr-dub-sw01.atlas.prod.ripe.net and the probe id is 1012917.

1 Like
2

I solved it… Apparently it tries to establish an ssh tunnel to the server on local port 8080; this was already in use by another (http server) process so it failed quietly and then tried to send its traffic that way instead, and failed…

3

Note that the probe’s “local http port” is nowadays configurable, see GitHub - RIPE-NCC/ripe-atlas-software-probe: Probe codebase of RIPE Atlas, a global network measuring Internet connectivity and reachability

1 Like