Process localizer (1) terminated with an error exit status (1) predector error
0
0
Entering edit mode
9 months ago
analyst ▴ 70

Dear all,

Predector command runs successfully for test data given in the manual:

Command: nextflow run -profile test,docker_sudo -resume -r 1.2.7 ccdmb/predector

However predector command for my data generates error:

Command: nextflow run -resume -r 1.2.7 -profile docker_sudo -config ./config.txt ccdmb/predector --proteome "/home/fungus/Data/check_predector/*.faa"

I have 145 proteomes of 7-9mb sizes i checked for three proteomes only but got error (please note that i have 96 cores server, 2tb storage, 440.5 GiB memory)

config.txt contains:

process {

  withLabel:cpu_low {
    cpus = 1
  }
  withLabel:cpu_medium {
    cpus = 4
  }
  withLabel:cpu_high {
    cpus = 96
  }

  withLabel:ram_low {
    memory = 2.GB
  }
  withLabel:ram_medium {
    memory = 8.GB
  }
  withLabel:ram_high {
    memory = 380.GB
  }
}

params {
  max_cpus = 90
  max_memory = 400.GB
}

Error:

Plus 4 more processes waiting for tasks… [91/8ed1aa] NOTE: Process apoplastp (1) terminated with an error exit status (137) -- Execution is retried (1) ERROR ~ Error executing process > 'localizer (1)'

Caused by: Process localizer (1) terminated with an error exit status (1)

Command executed:

run () { set -e TMP="tmp$$" LOCALIZER.py -e -i "$1" -o "${TMP}" 1>&2 cat "${TMP}/Results.txt"
rm -rf -- "${TMP}" } export -f run CHUNKSIZE="$(decide_task_chunksize.sh in.fasta "96" 100)" parallel --halt now,fail=1 --joblog log.txt -j "96" -N "${CHUNKSIZE}" --line-buffer --recstart '>' --cat run < in.fasta | cat > out.txt predutils r2js --pipeline-version "1.2.7" --software-version "1.0.3" -o out.ldjson localizer out.txt in.fasta

Command exit status: 1

Command output: (empty)

Command error: Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9
Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9
Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9
Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9 Error calling WEKA: Calling WEKA returned -9
Error calling WEKA: Calling WEKA returned -9 parallel: This job failed: run $PARALLEL_TMP parallel: This job failed: run $PARALLEL_TMP parallel: This job failed: run $PARALLEL_TMP
parallel: This job failed: run $PARALLEL_TMP Error calling WEKA: Calling WEKA returned -9 parallel: This job failed: run $PARALLEL_TMP parallel: This job failed: run $PARALLEL_TMP
parallel: This job failed: run $PARALLEL_TMP

Work dir:
/home/fungus/Apps/check_predector/work/b5/fcc9d7cfa77decd6c209b92955d602

Container: predector/predector:1.2.7

Tip: you can try to figure out what's wrong by changing to the process work dir and showing the script file named .command.sh

-- Check '.nextflow.log' file for details

predector fungus • 450 views
ADD COMMENT

Login before adding your answer.

Traffic: 3825 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6