Closed slsevilla closed 1 year ago
@slsevilla I and @nvlachos have seen this before. I believe the error is coming from the kraken step. The END_VERSIONS
and weird spacing for the kraken step shouldn't be in the collated_versions.yml
file. I don't know why that is happening though as I can't recreate the error (the only differences are I have a different database location obviously). There isn't some weird spacing or something that is being added to the end of the database argument you pass is there?
Hi - This is the exact command I'm running:
./nextflow run cdcgov/phoenix -r v1.0.0 -profile docker,test -entry PHOENIX --kraken2db /home/ubuntu/phoenix/
So to your question, no. There's no weird spacing I'm adding... just the absolute path of the phoenix db.
I'm finding the error is persistent even with trying a new dataset. I am attempting with a run now to bypass the issue by commenting out the requirement for the this version.yaml to be added to the final report, but I'm not sure if this will fix the problem.
from: ~/.nextflow/assets/cdcgov/phoenix/workflows/cdc_phoenix.nf
KRAKEN2_TRIMD (
FASTP_TRIMD.out.reads, "trimd", GATHERING_READ_QC_STATS.out.fastp_total_qc, []
)
// ch_versions = ch_versions.mix(KRAKEN2_TRIMD.out.versions)
The error is from the versions.yaml file being created, although I can't quite figure out why this is causing the issue here.
$ cat versions.yml
"PHOENIX:PHOENIX_EXTERNAL:KRAKEN2_TRIMD:KRAKEN2_TRIMD":
kraken2: 2.1.2
kraken2db: kraken2db
END_VERSIONS
I'd appreciate any additional thoughts you might have.
For anyone else who encounters this issue, while I don't understand why it's happening, but I do have a solution:
Edit the following file:
.nextflow/assets/cdcgov/phoenix/modules/local/kraken2.nf
Change the versions.yaml
command to the following:
echo -e "${task.process}:\n kraken2: \$(echo \$(kraken2 --version 2>&1) | sed 's/^.*Kraken version //; s/ .*\$//') \n kraken2db: $db" > versions.yml
This fixed the formatting issue for me, and allowed me to move to completion. Since it seems to be an issue I'm only having, and hasn't been reproducible for you all, I'm closing the issue.
Describe the bug CUSTOM_DUMPSOFTWAREVERSIONS is producing a
Command exit status: 1 error
.Impact Pipeline is failing when attempting to run this process.
To Reproduce Running in an AWS instance (Linux-based).
I'm attempting to run the test samples using the following command:
Problem Workflow process
Error details below:
Adding output of collated_versions.yml below:
Please let me know what other information you might need!