-
Notifications
You must be signed in to change notification settings - Fork 643
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
[Nextflow + Azure Batch] Unable to find size for VM name 'Standard_E4ads_v5' and location 'germanywestcentral' #5076
Comments
Hi @landroutsosAIE, it doesn't seem to appear in this list of VMs by region.. I've updated the list here: related to #2994 |
Hello @adamrtalbot. Thank you for help. I will wait for the pull request to be accepted. So it can't download the salmon folder from the previous step. We are running this pipeline in Seqera too and from the four same tasks, one succeeded, two didnt with exit 1 and one didnt with exit 137 (which i suppose is a RAM problem). We are using max memory 256gb. |
That's unusual, does the blob directory include the expected file? Does resume work? I presume the task that exited with error code 137 was running on a machine with 256gb of storage? When using Seqera Platform, you shouldn't need to specify any of this configuration. I would try and remove anything around configuring storage and batch accounts. |
Yes, the folder exists in the blob directory. I think the problem is with my Azure batch config for nextflow. it didnt used the high memory process VM series that I was assigning. I am now running the pipeline with only the high memory process VM (with 256 gb ram) and I will get back at you. I am using Seqera (-with-tower parameter) only for better monitoring of my pipeline. |
Can this be considered solved by #5100? |
Currently getting error 😱 :
|
Adding some logging it's failing to find the Azure VMs in a region:
|
Idiot useast vs eastus. Going to add another check for that 🤦 Done: #5108 |
Bug report
I am trying to use Azure batch with Nextflow and Seqera, but I cant initiate any job because of wrong VM name, location name or not matching any VM of this name at the specific region.
Expected behavior and actual behavior
I am running this command as a test to check my Azure batch config at the Nextflow level:
nextflow run nf-core/rnaseq -profile test,docker -c .nextflow/azure_batch_19_06.config --outdir "az://firstcontainer/testrun_19_06/" -w "az://firstcontainer/work_19_06" -with-tower
My config file:
The expected behavior was to run the rnaseq test correctly at Seqera, using Azure Batch for job scheduling and computational resources management, but it can't access the VMs I am specifying.
My Azure Batch quota is the following: 256 EADSv5 Vm Series,
Program output
The error is this:
The error at .nextflow.log is this:
Environment
What could be the issue here? Thanks in advance!
The text was updated successfully, but these errors were encountered: