# Errno::ENOMEM: Cannot allocate memory

**URL:** https://meta.discourse.org/t/errno-cannot-allocate-memory/43736
**Category:** Self-hosting
**Tags:** server-resources
**Created:** [May 5, 2016, 2:32pm UTC](https://meta.discourse.org/t/errno-cannot-allocate-memory/43736 "2016-05-05T14:32:01Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [May 5, 2016, 10:45pm UTC](https://meta.discourse.org/t/errno-cannot-allocate-memory/43736/7 "2016-05-05T22:45:16Z")

</div>

Set up a swap!

> [@Create a swapfile for your Linux server](https://meta.discourse.org/t/create-a-swapfile-for-your-linux-server/13880):
>
> bulb For servers with \<= 4GB of RAM, running ./discourse-setup will prompt for and automatically create a 2GB swapfile. Most cloud virtual machine providers do not set up swapfiles as part of their server provisioning. In particular, upgrading Discourse produces a lot of memory pressure. With a swap file, rather than randomly terminating processes with an out of memory error, things will slow down instead. Having a swap file is a cheap insurance policy that protects you from many other lo…

---

_[View the full topic](https://meta.discourse.org/t/errno-cannot-allocate-memory/43736)._
