# Error Exit code 137 () in fastp

**URL:** <https://help.galaxyproject.org/t/error-exit-code-137-in-fastp/11726>\
**Category:** Uncategorized\
**Tags:** troubleshooting, quality-control\
**Created:** [February 16, 2024, 2:36pm UTC](https://help.galaxyproject.org/t/error-exit-code-137-in-fastp/11726 "2024-02-16T14:36:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joana\_Morais](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/joana_morais/32/5227_2.png) [@Joana\_Morais](https://help.galaxyproject.org/u/Joana_Morais)\
**Post date:** [February 16, 2024, 2:36pm UTC](https://help.galaxyproject.org/t/error-exit-code-137-in-fastp/11726/1 "2024-02-16T14:36:56Z")

</div>

Hello. I’m trying to run fastp to trim my reads (quality and length). However, I received the following errors:

_Fatal error: Exit code 137 ()_

_Detecting adapter sequence for read1…_  
_/jetstream2/scratch/main/jobs/55693473/tool\_script.sh: line 23: 297687 Killed fastp --thread ${GALAXY\_SLOTS:-1} --report\_title ‘fastp report for fasta\_conc\_fastq.fastq’ -i ‘fasta\_conc\_fastq.fastq’ -o first.fastq_

_slurmstepd: error: Detected 1 oom-kill event(s) in StepId=1461577.batch. Some of your processes may have been killed by the cgroup out-of-memory handler._

I believe they are related to use of memory. Is there a way to increase memory? The file I’m using is 209,3 MB and I was using phred quality \> 15 and length \> 100pb.

---

<div class="post-metadata">

**Author:** ![jennaj](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/jennaj/32/27_2.png) [@jennaj](https://help.galaxyproject.org/u/jennaj)\
**Post date:** [February 19, 2024, 7:13pm UTC](https://help.galaxyproject.org/t/error-exit-code-137-in-fastp/11726/2 "2024-02-19T19:13:14Z")

</div>

Hi @Joana_Morais

Computational resources are fixed for everyone, plus your file is not too large. Something else is going on.

Some of the jobs at [UseGalaxy.org](http://UseGalaxy.org) failed with this error last week. The solution for those errors are to try a rerun.

If the job fails again, consider checking the content of the input reads since data problems can also _sometimes_ lead to errors. “Problems” could be a truncated file, incomplete upload, or the wrong datatype. **FastQC** and **Fastq info** are good choices for integrity checks.

Xref: [GTN Materials Search](https://training.galaxyproject.org/training-material/search2?query=quality) query=quality