A lot of users have come across failed rebuilds recently (since September 2024) with the command was killed with SIGKILL error, even though the servers have more than 1 GB RAM (even 4 GB RAM). https://meta.discourse.org/search?q=%22command%20was%20killed%20with%20SIGKILL%22 Advice has been given to create (or increase) a swap file, and it fixed the issue: [imagem] Failed new install Self-hosting Could it be memory? Do you have swap? Can you add 4G of swap? [imagem] Moving to New Server woes Support That was it. I ended up creating a file based swap and turning it on and that fixed any of my issues! I ended up doing a new install and a backup restore to get it all working, but everything is working now. I appreciate the help. [imagem] Rebuild fails with exit 1: ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL Support Well, I changed swap from 2G to 4G, and rebuilding went thru. So mayby it was again matter of amount of RAM. Or it was a fluke. And then we are back in FAQ-topic: how much RAM does Discourse really need — because swapfile is de facto part of total amount RAM, and now it looks like the actual need is 11+ GB for small forum flushed_face [imagem] Rebuild failed because there was no swap Support Is there a possibility this SIGKILL came from an out of memory condition - the OOM killer at work? (dmesg might be able to answer) I myself have encountered this problem on at least two of my 7 forums, on machines having 2 to 4 GB RAM. Either the requirements have changed, in which case the documentation should be updated, or there’s something wrong. (I don’t know where to put this topic, I thought about #bug, #installation, #site-feedback… Please move it if necessary :smile:)

[imagem] Canapin: Either the requirements have changed, in which case the documentation should be updated, or there’s something wrong. Agreed. Though the setup for the VM i was using really should have some swap, the machine should have had more than enough RAM to handle the build. Maybe just call out the need for a swap partition/file in the docs?

discourse-setup offers to create a swap file automatically if it detects 2GB or less of memory. discourse-setup e42fa9711 echo "WARNING: Discourse requires at least 2GB of swap when running with 2GB of RAM" echo "or less. This system does not appear to have sufficient swap space." echo echo "Without sufficient swap space, your site may not work properly, and future" echo "upgrades of Discourse may not complete successfully." echo echo "Ctrl+C to exit or wait 5 seconds to have a 2GB swapfile created."

Hi gerhard, I’m aware of this, but this doesn’t address the issue unfortunately. Instances with more than 2 GB RAM will experience the rebuild error, and even instances with < 2 GB RAM who already had a 2GB swap file created by discourse-setup experiences the issue as well, like @alltiagocom’s instance. Plus, this problem seems quite recent and was never reported before September 2024, according to the search.

Yes, it does. But we are in a situation, where it should create at least 2 GB of cache every time there is less than 8 GB of RAM. I would guess it comes from the fact that every single forum will use plugins. Or something, because I don’t understand mechanics of these things. It should be made clearer that those values are real minimums in deed, and if an admin decides to use different plugins, more RAM and cache are needed. I mean, we have far too many topics where the reason for the issues is a lack of memory.

[imagem] gerhard: discourse-setup offers to create a swap file automatically if it detects 2GB or less of memory. This seems to need to be increased. As @Canapin pointed out with my topic having 4g of ram was not sufficient. And as I mentioned in my topic the instructions for adding a swap file should be added to git hub install instructions even if just an option if 4g of ram or less.

@david recently worked on this space, our memory bottleneck is during asset compilation and we now have a low memory mode as well. My understanding is that 2gb should still be supported, this is something we will investigate.

Closing in favour of: [imagem] High rebuild memory requirements: April 2025 edition Self-hosting We just landed this commit which should hopefully improve the situation. Please let us know how you get on! (it’ll hit tests-passed in the next ~30 mins) When testing with a memory-constrained docker container locally, I can now get a successful build with -m 1600m. Before this change, the minimum I could achieve was -m 3000m.

Os requisitos do Discourse mudaram recentemente?

Suporte ao Produto Instalação

david (David Taylor) 4 Abril , 2025 12:54 8

Fechando em favor de:

Tópico		Respostas	Vistas
Error rebuilding on 2GB RAM without swap Self-hosting server-resources	8	723	3 Outubro , 2023
High rebuild memory requirements: April 2025 edition Self-hosting hosting	32	1623	15 Fevereiro , 2026
Rebuild fails with exit 1: ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL Product Support	15	1129	2 Março , 2025
Discourse Swap Memory (1GB Warning) Product Support server-resources	7	3565	29 Abril , 2021
1GB ram Discourse setup / swap file error Product Support server-resources	6	1500	27 Outubro , 2017

Os requisitos do Discourse mudaram recentemente?

Related topics