-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR:root:Resource job-cloud-split-local-ssd.yaml.template is missing from the package #15
Comments
Hi @arminmm91, thank you for trying elastic-blast and we are sorry you ran into a problem. Are you by any chance working on Windows? If so, I'm sorry to report that ElasticBLAST isn't supported on Windows at this time. We are looking into your problem, but cannot promise a quick solution. In the mean time you can try it using the AWS or GCP cloud shell from a Windows machine and run elastic-blast there. I hope this helps. |
thanks for your response @boratyng, I was trying to run it on PowerShell, but I tried WSL, still did not work. |
We looked closer into your issue and it looks like elastic-blast does not install correctly in Windows. A few files are missing and this results in the error message that you saw. There are additional small issues, so at this point elastic-blast will not run in Windows. Sorry. Unfortunately I am not very familiar with WSL, but here are a few suggestions:
It is relatively easy to run elastic-blast in cloudshell either in AWS or GCP, and you can access cloudshell from Windows. Please, consider running elastic-blast in cloudshell. Here is some information about it: |
Thank you for the suggesting cloud shell. Although everything should be working, but I submitted a job, 15,000 sequences with this configuration(the actual path of bucket was provided when submitted): [cluster] [blast] and when I check gcloud container clusters list, a job is still running, however, kubectl get pods says there two that both completed one with error the other completed with 0 error, when I check the results, there is none. Please let know if you see any mistakes on my side. |
Unfortunately
If you are still running into trouble it would be helpful for us if you attached |
@arminmm91 , we noticed that the default Kubernetes version was updated in GCP and it may be causing issues for elastic-blast. If you are still having issues adding
|
Hi @boratyng, I managed to work with swissprot database through google cloud and shell. However, for nt and nr databases it gave this error: |
Hi @arminmm91, can you attach
Please, also attach or post result of this command:
Thanks. |
Hi @boratyng, please see attached all the log files and metadata (only the important ones), I replaced the actual bucket name and project with 'xxx': metadata_elastic-blast-config.txt This command, $ tar czf elastic-blast-diagnostics.tgz logs metadata returned this: Best, |
@arminmm91, I found one problem. It looks like you are trying to run a blastn search with |
Hi @boratyng, thanks again but the change did not lead to a successful run. I've attached the log file: metadata_FAILURE_details (2).txt name = blastn |
Hi @arminmm91, you left the |
Hi @boratyng, I tried -task megablast as well, forgot to mention, but still got the same error. |
@arminmm91, Also, I see that you set |
Hi,
I've installed the elastic-blast package and all it's dependences, but when I want to check the version as a test for its executability, it returns this error:
python ..elb-venv\Scripts\elastic-blast --version
ERROR:root:Resource job-cloud-split-local-ssd.yaml.template is missing from the package. Please re-install ElasticBLAST
Also, remove and installed the package a couple of times, did not work.
Please let me possible solutions or opinions.
The text was updated successfully, but these errors were encountered: