Closed parlar closed 5 years ago
seems that this is the problem.
Tried again on an Ubuntu 18.04 machine outside the corporate network, then it works. Certificate issue?
One more piece of information: the conda installation of bioconductor-genomeinfodbdata works if I create a separate environment but not when installing into the bcbio base environment. Wierd.
EDIT: I may have used -c biobuild
instead of -c bioconda
when it worked. When verifying it did not..
Pär; Thanks for the report and sorry about the issues. My suggestion for debugging is to try running the problem script outside of conda:
/home/pela09/bcbio/anaconda/bin/.bioconductor-genomeinfodbdata-post-link.sh
This is a shell script that actually does the install download. Since the data files for R in this case are large, it isn't directly in the bioconda package but rather part of this downstream step. It sounds like there is something in your network environment blocking this but it's hard to know what from just the error message. Hopefully running it separately will reveal some clues to help debug and avoid. Thanks much for the report and help debugging.
I should give an update on this:
The error is due to that the ca-certificate path is not correctly set. Even if I set ca-certificates explicitly in conda it fails. I have entered an issue here: https://github.com/conda/conda/issues/8653 .
Now the bioconductor-genomeinfodbdata package has been modified to use curl (instead of wget) but the problem remains since it's due to conda not seeing certificates. But by setting export SSL_CERT_FILE=/path/to/ca.pem
, however, the package can be installed and then everything works.
It it has nothing todo with bioconductor or bcbio, but I thought I should make an entry here if anyone else encounters this issue.
Another update:
mingwandroid wrote (https://github.com/conda/conda/issues/8653) "Conda's ssl settings pertain only to conda itself and not to and other packages you can install via conda."
This means that the installation will always fail if you're inside a corporate network that depends on a correctly set ca-cert. I have proposed here https://github.com/bioconda/bioconda-recipes/issues/13846 that the conda package installation is modified to set ca-cert for curl if it's set in conda. Don't know if this is the right way of fixing it?
Pär;
Thanks for investigating this. It sounds like the export SSL_CERT
approach to point at the valid certification for your environment is a work around, is that right? If so, it seems like the best approach to avoid these and we could add a note to the documentation so folks know to look at that as an option if they're in a restricted environment.
If the SSL_CERT_FILE
env variable is still visible from within the conda env I guess it must work. I can double check on Monday.
Thanks, let us know if that ends up working so we can add in the documentation. Nice one finding a possible workaround.
Tried to install using the latest stable version of bcbio-nextgen but it exists with an error. See further down below for complete error message.
System is Centos 7.6.1810
Installation of bioconductor-genomeinfodbdata-1.2.0 exits with the following error:
Have tried to install this package from a different bioconda label but the same error persists. Have also downgraded Python to 3.6.7 but that did not solve anything.
Complete error msg: