Apply Orbit Operator fails for QC Sentinel-1 server down

Why SNAP v8.0 tries still to download the Sentinel-1 POEORB from qc.sentinel1.eo.esa.int instead of the url set in the snap.aux.properties?

OrbitFiles.sentinel1POEOrbitPath = {AuxDataPath}/Orbits/Sentinel-1/POEORB OrbitFiles.sentinel1RESOrbitPath = {AuxDataPath}/Orbits/Sentinel-1/RESORB
OrbitFiles.sentinel1POEOrbit_remotePath = http://step.esa.int/auxdata/orbits/Sentinel-1/POEORB/
OrbitFiles.sentinel1RESOrbit_remotePath = http://step.esa.int/auxdata/orbits/Sentinel-1/RESORB/

Today exacty now the qc.sentinel1.eo.esa.int is down but the back up aux.sentinel1.eo.esa.int is up and running as well as the step server … however SNAP only tries to download from qc.sentinel1 website which failed today.

####################################################################
ERROR MESSAGE:
Exception calling QC Rest API: Connect to qc.sentinel1.eo.esa.int:443 [qc.sentinel1.eo.esa.int/131.176.235.71] failed: Connection timed out (Connection timed out)
WARNING: org.esa.s1tbx.sar.gpf.orbits.ApplyOrbitFileOp: Connect to qc.sentinel1.eo.esa.int:443 [qc.sentinel1.eo.esa.int/131.176.235.71] failed: Connection timed out (Connection timed out)
Exception calling QC Rest API: Connect to qc.sentinel1.eo.esa.int:443 [qc.sentinel1.eo.esa.int/131.176.235.71] failed: Connection timed out (Connection timed out)
Connect to qc.sentinel1.eo.esa.int:443 [qc.sentinel1.eo.esa.int/131.176.235.71] failed: Connection timed out (Connection timed out) due to Connection timed out (Connection timed out)
done.

Error: [NodeId: Apply-Orbit-File] Connect to qc.sentinel1.eo.esa.int:443 [qc.sentinel1.eo.esa.int/131.176.235.71] failed: Connection timed out (Connection timed out) due to Connection timed out (Connection timed out)
#################################################################

Can this please be quickly fixed? @marpet, @jun_lu, @lveci? @mengdahl

2 Likes

15 posts were merged into an existing topic: Orbit file timeout (March 2021)