I am getting the following error while extracting my private collection (running it in Terrascope jupyter environment) -
RetryError: HTTPSConnectionPool(host=‘ewoc-rdm-api.iiasa.ac.at’, port=443): Max retries exceeded with url: … (Caused by ResponseError(‘too many 500 error responses’))
Is the server down at this time, or is it some other error which I am not addressing
Hi there,
there’s indeed ongoing issues at the CDSE side, which is reported here. Even though it’s mentioned that the issue is resolved, we see it reoccurring frequently in the past few days, which may explain the issue you’re experiencing.
At this point, we can only recommend to keep an eye on the official CDSE channels and retry the extraction workflow until it works again. Apologies for the inconvenience!
It seems to be running fine locally, but when i run it locally on Windows, it throws me module not found error for module “grp” in run_extractions code.
When I run it on Terrascope, only then I am facing this issue.
What do you mean by running locally? Extractions will run on CDSE for access to the satellite and auxiliary data. Which part of the code is giving you the issue?
Here, running locally means in my local machine on VSCode. Following is the snapshot of the error that I get -
As i found out, that grp module is not available on Windows systems, as it is specific to Unix-like operating systems
we’re investigating the use of this module, but I’m a bit confused as this thread originally was started for the server issues. Your other thread is on the grp module. They’re probably unrelated?
Yes, thats correct. Apologies for the cross post. I’ll put the same message in the correct thread.
Hi! We indeed experienced some connectivity issues when fetching data from our Reference Data Module. On our side, things are working smoothly again. Could you try again and notify us if this connection error persists?
FYI: after uploading your private dataset into RDM, it takes a couple of minutes before the data is ready for download, so trying again after a while for a freshly uploaded dataset might also resolve your issue.
Hope this helps!
There is no connection error now. Thanks. Although I am having similar issues when I run it on Terrascope
