Having rebuilt discourse today, the CPU on my droplet is stuck at 100% and I am getting a 504 Gateway Time-out error. In terminal I have checked which processes are causing the issue and this is what I see: [Screenshot 2026-02-11 at 13.19.56] So it appears to be an issue with docker and a pitchfo…

Does upgrading your Droplet’s specs help?

How long have you waited on this state? We moved to a new webserver today, and sometimes it takes a little longer to fully boot.

Thanks. I didn’t realise that I could increase the memory on the droplet and then reverse it (as long as the disk size isn’t changed). I increased the memory temporarily to 8GB and everything started working as expected, with a CPU of 2-5% (see screenshot below), but when I reverted back to 2GB, whi…

I’ve waited 30 minutes or more.

We’ve just merged a change that should fix the issue: DEV: Allow pitchfork workers to take more time to boot (#37721) committed 02:10PM - 11 Feb 26 UTC (UTC) [画像] Flink …

Sure. When can I know when it’s ready?

You can check Commits · discourse/discourse · GitHub to see if the commit is in the list. Otherwise, I’ll let you know when I see it’s ready :slight_smile:

OK, thanks for letting me know.

Thanks. Everything’s working now with 2GB of memory.

Discourse がリビルド後に 504 Gateway Time-Out エラーと CPU 100% でスタックした

サポート

loic (Loïc Guitaut) 2026 年 2 月 11 日午後 2:35 11

修正はlatestに適用されました。

トピック		返信	表示
Emergency help - freeCodeCamp Discourse down Self-hosting	20	2282	2019 年 5 月 5 日
Discourse stopping working - CPU/RAM load? Support	9	1108	2023 年 4 月 24 日
CPU, Memory and Swap at 100% Self-hosting server-resources	7	676	2021 年 12 月 8 日
504 Gateway Time-out errors with 2 million post migrated vBulletin forum Self-hosting	4	1107	2021 年 12 月 7 日
Server not response (DO SGP1) Self-hosting	16	2210	2024 年 6 月 8 日

Discourse がリビルド後に 504 Gateway Time-Out エラーと CPU 100% でスタックした

関連トピック