You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Appologize if this is not the right place to post on precompiled binaries.
I successfully downloaded and install precompiled binaries on a CentOS 7 linux server.
I could launch almost all process describe in the README.md of this repo (very helpful, thanks!).
Yet I met some issues with the download of CAMS data.
Here is the command I ran: ./camsdownload -d 20201001 -f 20201001 -a /<my data directory>/CNES_MAJA/CAMS -w /<my data directory>/CNES_MAJA/CAMS/Archive -p s2
And here are the outputs:
Number of days = 1
==================================
Downloading files for date 2020-10-01 00:00:00
==================================
Python socket module was not compiled with SSL support. Aborting...
I could not replicate the issue on my end using the embedded python exe. I will forward it to the developers to check if they can reproduce it.
Should you not want to pass by a dedicated docker img, you can just use a conda environment and call cams_download.py (located in /lib) directly using the new python exe.
Hello,
Appologize if this is not the right place to post on precompiled binaries.
I successfully downloaded and install precompiled binaries on a CentOS 7 linux server.
I could launch almost all process describe in the README.md of this repo (very helpful, thanks!).
Yet I met some issues with the download of CAMS data.
Here is the command I ran:
./camsdownload -d 20201001 -f 20201001 -a /<my data directory>/CNES_MAJA/CAMS -w /<my data directory>/CNES_MAJA/CAMS/Archive -p s2
And here are the outputs:
Making some search on the internet, I found that issue could be that the embeded Python is not built with ssl support (see https://www.programmersought.com/article/5708542317/).
I could work around this by taking the code related to CAMS download and put all that in a docker with a python release that worked fine.
Is that issue only happening for me?
Thanks.
The text was updated successfully, but these errors were encountered: