# 3.1.x to 3.2.0 upgrade hangs/fails on 1GB instance

**URL:** https://meta.discourse.org/t/3-1-x-to-3-2-0-upgrade-hangs-fails-on-1gb-instance/293743
**Category:** Self-hosting
**Created:** [February 1, 2024, 6:18am UTC](https://meta.discourse.org/t/3-1-x-to-3-2-0-upgrade-hangs-fails-on-1gb-instance/293743 "2024-02-01T06:18:18Z")
**Posts on this page:** 1
**Showing post:** 33

<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: [February 13, 2024, 5:05pm UTC](https://meta.discourse.org/t/3-1-x-to-3-2-0-upgrade-hangs-fails-on-1gb-instance/293743/33 "2024-02-13T17:05:16Z")

</div>

> [@pfaffman](#):
>
> Definitely no plugins with 1GB of ram

As an extreme shorthand I can see why you’d say this, but don’t you agree that the go/nogo for running Discourse is RAM+swap? 1+3 is just as good as 2+2 from a point of view of go/nogo.

It’s only performance (responsiveness) which cares how much RAM you have.

RAM+swap is the right thing to check and test. Memory=RAM+swap.

BTW if something is not working with no obvious evidence as to why, and especially if you suspect memory shortage, it’s worth checking for the out-of-memory killer, also known as the OOM-killer. I recommend

```plaintext
dmesg|egrep -i "memory|oom|kill"

```

Edit: for convenience I’ll add that to my list of standard instant diagnostics:

```plaintext
cat /etc/lsb-release
uptime
df -h /
free
vmstat 5 5
dmesg|egrep -i "memory|oom|kill"
ps auxrc

```

---

_[View the full topic](https://meta.discourse.org/t/3-1-x-to-3-2-0-upgrade-hangs-fails-on-1gb-instance/293743)._