Open landroutsosAIE opened 5 months ago
Hi @landroutsosAIE, it doesn't seem to appear in this list of VMs by region.. I've updated the list here:
https://github.com/nextflow-io/nextflow/pull/5100
related to https://github.com/nextflow-io/nextflow/issues/2994
Hello @adamrtalbot. Thank you for help. I will wait for the pull request to be accepted.
I have an other problem with the same pipeline. I changed the Azure Batch config and now it works until the Salmon quant step. It stops with exit status 1 and the real error shows up at command.log file:
Unable to download path: https://<ourblobstorage>/test_run_07_01/7a/4ac8cca20ea799d9c65917be044a73/salmon
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 https://github.com/nextflow-io/nextflow/pull/5100?
Currently getting error 😱 :
ERROR ~ Error executing process > 'sayHello (3)'
Caused by:
Cannot find a VM for task 'sayHello (3)' matching these requirements: type=Standard_E4-2ads_v5, cpus=1, mem=-, location=useast
Adding some logging it's failing to find the Azure VMs in a region:
Jul-03 11:17:09.642 [Task submitter] DEBUG n.c.azure.batch.AzBatchTaskHandler - [AZURE BATCH] Submitting task sayHello (4) - work-dir=az://scidev-useast/aa/a13d6b287c3b1e178396256bce01be
Jul-03 11:17:10.120 [Task submitter] DEBUG n.cloud.azure.batch.AzBatchService - [AZURE BATCH] guessing best VM given location=useast; cpus=1; mem=null; family=Standard_E4-2ads_v5
Jul-03 11:17:10.120 [Task submitter] DEBUG n.cloud.azure.batch.AzBatchService - [AZURE BATCH] Finding best VM given location=useast; cpus=1; mem=null; family=Standard_E4-2ads_v5
Jul-03 11:17:10.121 [Task submitter] WARN n.cloud.azure.batch.AzBatchService - [AZURE BATCH] Unable to find Azure VM names for location: useast
Jul-03 11:17:10.121 [Task submitter] DEBUG n.cloud.azure.batch.AzBatchService - [AZURE BATCH] Found 0 VM types in location useast
Jul-03 11:17:10.121 [Task submitter] DEBUG n.cloud.azure.batch.AzBatchService - [AZURE BATCH] Listing VM families
Jul-03 11:17:10.121 [Task submitter] DEBUG n.cloud.azure.batch.AzBatchService - [AZURE BATCH] Found 0 VM types matching the criteria
Idiot
useast vs eastus. Going to add another check for that 🤦
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!