2024-01-14 22:15:13.479 UTC [4179] LOG: using stale statistics instead of current ones because stats collector is not responding node:events:492 throw er; // Unhandled 'error' event ^ Error: write EPIPE at afterWriteDispatched (node:internal/stream_base_commons:160:15) at write…

How much swap have you added? You’ll need at least 2GB. In general I feel Discourse now needs a 4GB VPS, but your mileage may vary …

As a general rule, if you’re posting a section of the log, you should include 100 more lines from before where you think you should start, because the actual error is almost always earlier than you might think. Please post a full log, or much more than you did. Posting the output of free df -h un…

[Screenshot 2024-01-16 002112] Here is the configuration of my aws ec2 instance.

Thanks. Please post a more complete log. Some process has died, causing some other process to fail to write to it. It’s a good idea also to look in the kernel logs for out of memory conditions dmesg | egrep -i "memory|oom" and if you find any please post the surrounding context dmesg | egrep -i9…

nohup: ignoring input x86_64 arch detected. Ensuring launcher is up to date Fetching origin Launcher is up-to-date 2.0.20231218-0429: Pulling from discourse/base Digest: sha256:468f70b9bb4c6d0c6c2bbb3efc1a5e12d145eae57bdb6946b7fe5558beb52dc1 Status: Image is up to date for discourse/base:2.0.2023121…

root@ip-172-31-26-149:/var/discourse# dmesg | egrep -i "memory|oom" [ 0.030234] ACPI: Reserving FACP table memory at [mem 0xfc00c440-0xfc00c533] [ 0.030236] ACPI: Reserving DSDT table memory at [mem 0xfc003940-0xfc00c3bd] [ 0.030238] ACPI: Reserving FACS table memory at [mem 0xfc003900-0xfc…

Hii @Ed_S and @merefield Thank you so much for your reply. My issue is not yet got resolved yet. Can you please help me out to this. I will be thankful to you guys forever. Im using aws ec2 instance with 1GB ram, 30GB EBS storage ans still facing the issue. [image] [image] [image] Please go …

Oh, missed this, you need to be on Jammy 22.x, and consider at least doubling your RAM.

Thanks for the extra detail. Note that A 137 code is issued when a process is terminated externally because of its memory consumption So there is a problem with the amount of virtual memory. It’s not strictly about RAM, but you either need more RAM or more swap. Or, possibly, you need to change…

By the way, sometimes there has been an unfortunate change in the Discourse software, and it is very helpful to be able to track down what has gone wrong, which can help other people. Sometimes, you might just be in need of a quick fix, without investigation or explanation. In that case, your hosti…

Problème lors de la configuration de Discourse sur mon instance AWS EC2 Ubuntu 20, ebs 30 Go RAM 1 Go

Soutien Installation

merefield (Robert) Janvier 16, 2024, 11:19 9

Oh, j’ai manqué ça, vous devez être sur Jammy 22.x, et envisager au moins de doubler votre RAM.

Sujet		Réponses	Vues
Failed to upgrade discourse instance to Feb 15 2022 Self-hosting server-resources	30	2807	Mars 23, 2022
Bootstrapping Discourse hangs on Redis "ready to accept connections" on Amazon EC2 Self-hosting	9	2153	Avril 27, 2015
3.1.x to 3.2.0 upgrade hangs/fails on 1GB instance Self-hosting	34	1589	Février 23, 2024
Discourse not using much RAM Self-hosting server-resources	31	1617	Août 8, 2021
Failed new install Self-hosting	8	256	Mars 19, 2025

Problème lors de la configuration de Discourse sur mon instance AWS EC2 Ubuntu 20, ebs 30 Go RAM 1 Go

Sujets connexes