# Memory allocation issue

**URL:** <https://community.seqera.io/t/memory-allocation-issue/601>\
**Category:** Ask for help\
**Created:** [March 26, 2024, 2:08pm UTC](https://community.seqera.io/t/memory-allocation-issue/601 "2024-03-26T14:08:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![DavYang](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/davyang/32/569_2.png) [@DavYang](https://community.seqera.io/u/DavYang)\
**Post date:** [March 26, 2024, 2:08pm UTC](https://community.seqera.io/t/memory-allocation-issue/601/1 "2024-03-26T14:08:43Z")

</div>

Hi guys, I am trying to run the following pipeline ([GitHub - PengNi/ccsmethphase: Methylatino phasing using PacBio CCS reads](https://github.com/PengNi/ccsmethphase?tab=readme-ov-file#Usage)) on my school’s cluster but am unable to move past a memory allocation issue. I’ve been trying to edit the config file to run singularity and request more CPUs accordingly, but my program errors out saying not enough CPUs are available. There are more than enough resources on the cluster side of things and so I think the issue is with how the resources are being requested (?). Would appreciate some insight into this:

Error executing process \> ‘CheckGenome (CheckGenome)’

Caused by:  
Process requirement exceed available CPUs – req: 8; avail: 1

---

<div class="post-metadata">

**Author:** ![mribeirodantas](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/mribeirodantas/32/235_2.png) [@mribeirodantas](https://community.seqera.io/u/mribeirodantas)\
**Post date:** [March 26, 2024, 2:19pm UTC](https://community.seqera.io/t/memory-allocation-issue/601/2 "2024-03-26T14:19:45Z")

</div>

If it’s a cluster, I wonder if you’re not trying to run it from the login node (which usually has resource limitations). Does your cluster use a workload manager such as SLURM or PBS? That could be a reason for such small availability of resources in a supposedly powerful infrastructure.

---

<div class="post-metadata">

**Author:** ![DavYang](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/davyang/32/569_2.png) [@DavYang](https://community.seqera.io/u/DavYang)\
**Post date:** [March 27, 2024, 2:00am UTC](https://community.seqera.io/t/memory-allocation-issue/601/3 "2024-03-27T02:00:55Z")

</div>

Hi Marcel,

The cluster Im using uses SLURM. In the past, I have not had this issue when trying to run nextflow pipelines.

---

<div class="post-metadata">

**Author:** ![mribeirodantas](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/mribeirodantas/32/235_2.png) [@mribeirodantas](https://community.seqera.io/u/mribeirodantas)\
**Post date:** [March 27, 2024, 12:13pm UTC](https://community.seqera.io/t/memory-allocation-issue/601/4 "2024-03-27T12:13:41Z")

</div>

Could you please run the command below in your shell and let me know what value is returned?

```auto
echo "$(grep -c processor /proc/cpuinfo)"

```

Are you setting `slurm` as the executor somewhere? For example, in `nextflow.config` with `process.executor = 'slurm'`, or `executor = 'slurm'` in your processes.
