- changed status to resolved
Error: KMA did not run as expected
KMA seems to be running into a core-dumping issue when I’m trying to analyze my metagenomic paired-end reads (total=65 Mio reads) on ResFinder.
I have already rerun ‘python3 INSTALL.py’ from inside db_resfinder and I did see filenames with suffix ‘.length.b’ being created there. Below is the command-line I used:
python3 /home/tools/resfinder/run_resfinder.py -o resfinder_output_reads -s “Other” -l 0.8 -t 0.9 --acquired -ifq ReadA_1.fastq ReadA_2.fastq -k /home/tools/resfinder/kma/kma
Below is the error message I got and under “KMA finished with the following response”, I found only a couple of blank lines. A core dumping file starting with 'core.XXXX” was found inside the main working directory after this error message was displayed.
“Error: KMA did not run as expected.
KMA finished with the following response:”
I tried to run the above on my computational cluster node with --mem=100G --cpus-per-task=12. Resfinder works fine for me though when running in BLAST mode with a metagenomic assembly fasta file as the input. Any help here would be appreciated.
Comments (1)
-
reporter - Log in to comment
I installed kma from the latest main git branch (as per the instructions from the developer Phillip; Issue addressed in detail here on the kma page-https://bitbucket.org/genomicepidemiology/kma/issues/41/error-kma-did-not-run-as-expected)