error
Closed this issue · 11 comments
NOTE: Process BETTERCALLSAL_DB:DOWNLOAD_PDG_METADATA (dl_pdg_metadata.py)
terminated with an error exit status (127) -- Execution is retried (1)
ERROR ~ Error executing process > 'BETTERCALLSAL_DB:DOWNLOAD_PDG_METADATA (dl_pdg_metadata.py)'
Caused by:
Process BETTERCALLSAL_DB:DOWNLOAD_PDG_METADATA (dl_pdg_metadata.py)
terminated with an error exit status (127)
Exit status 127 is generally a $PATH issue. What's the memory of the system where you are running it? Can you also upload the .nextflow.log file from where you started this pipeline? It should contain some additional details
Hello Chris,
Please attach the .nextflow.log
file to this issue. It should be in the same directory from where you executed the workflow. Can you paste the command you are trying to execute?
Thanks,
Kranti
what is the line to display the log file? El mar, 12 dic 2023 a las 16:35, Kranti Konganti @.>) escribió:
…
Hello Chris, Please attach the .nextflow.log file to this issue. It should be in the same directory from where you executed the workflow. Can you paste the command you are trying to execute? Thanks, Kranti — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJWAA4DPXWQFXSYNKYKUGXLYJDL45AVCNFSM6AAAAABAR3FXSOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJSHEZDCOBZG4 . You are receiving this because you authored the thread.Message ID: @.>
Just do cat .nextflow.log
from where you ran that cpipes .......
command and it should print the output. Paste the output here
Ok. You need to select one of the profiles. If you are running this on a single machine and not a cluster, add -profile stdkondagac
. For slurm
cluster, you can use one of the pre-defined profiles, -profile konda
.
For your single 1TB machine, you can try:
Ex:
cpipes --pipeline bettercallsal_db --pdg_release PDG000000002.2727 --output /home/chris_franco/bin/bases_de_datos/better_db/ -profile stdkondagac -resume
The -resume
option will resume the workflow from last failed step when you re-execute the same command.
Please note that the bettercallsal_db
workflow creates at least 500 to 1000 steps, so it may take a really long time on a single machine. You can download one of the pre-created databases for an older PDG release: https://cfsan-pub-xfer.s3.amazonaws.com/Kranti.Konganti/bettercallsal/PDG000000002.2537.tar.bz2, then do tar -jxvf PDG000000002.2537.tar.bz2
.
Thanks,
Kranti
You need to also make sure, you have micromamba
installed. Running the workflow via micromamba
software provisioning is preferred as it does not require any sudo
or admin
privileges or any other configurations with respect to the various container providers.
-
To install
micromamba
for your system type, please follow these installation steps and make sure that themicromamba
binary is made available in your$PATH
. -
Just the
curl
step is sufficient to download the binary as far as running the workflows are concerned. -
Once you have finished the installation, it is important that you downgrade
micromamba
to version1.0.0
.
micromamba self-update --version 1.0.0
Ok, delete the dl_pdg_metadata.py
inside the bin
folder and replace it with the script attached in this comment. Try again and let me know if it worked. If it works, then, I am going to patch the release. Also, please note that PDG000000002.2727
does not exist at NCBI anymore.
Try using --pdg_release latest_snps
when you call the cpipes ..........
command.
Note: Please make sure you rename the extension of the script from .txt
to .py
after you place it inside the bin
folder.