# Cannot rebuild app

**URL:** <https://meta.discourse.org/t/cannot-rebuild-app/359582>\
**Category:** Product Support\
**Created:** [March 31, 2025, 5:57am UTC](https://meta.discourse.org/t/cannot-rebuild-app/359582 "2025-03-31T05:57:46Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)\
**Post date:** [April 2, 2025, 11:19am UTC](https://meta.discourse.org/t/cannot-rebuild-app/359582/8 "2025-04-02T11:19:26Z")

</div>

Thanks… It’s still a bit of a mystery to me. But I would strongly recommend running with overcommit. You can set it now with

`sudo sysctl vm.overcommit_memory=1`

but to set it also on reboot might take a little more effort. It may make everything work, in which case making it persistent is the right thing. It looks like I did it by making a one-line file:

```plaintext
# cat /etc/sysctl.d/90-vm_overcommit_memory.conf 
vm.overcommit_memory=1

```

If that doesn’t help, it feels like some watchdog or quota is looking out for resource over-use and killing processes. Possibly a good look at the full dmesg output will help - if you’ve recently had the failure, perhaps the last 100 lines might give a clue.

---

_[View the full topic](https://meta.discourse.org/t/cannot-rebuild-app/359582)._