Discourse 遇到 504 Gateway Time-Out 错误且重建后 CPU 占用 100%

loic · 2026年二月11日 14:28

我们刚刚合并了一个应该可以修复该问题的更改：

DEV: Allow pitchfork workers to take more time to boot (#37721)

committed 02:10PM - 11 Feb 26 UTC

On constrained hardware/environments, the splay we added for Pitchfork’s workers… isn’t always enough and they hit the spawn timeout which is 10 seconds by default. This changes the default to 60 seconds, which should give plenty of time for booting even in the worst conditions. Unicorn didn’t have this timeout, explaining why we never saw this phenomenon before. The `APP_SERVER_SPAWN_TIMEOUT` env var can be used to lower or increase the timeout value.

它应该很快就会在 latest 版本中发布，修复可用后您能否尝试更新您的 droplet？

話題		回覆	觀看
Emergency help - freeCodeCamp Discourse down Self-hosting	18	2437	2017年二月22日
Discourse stopping working - CPU/RAM load? Support	7	1184	2019年九月8日
CPU, Memory and Swap at 100% Self-hosting server-resources	6	749	2021年十一月8日
504 Gateway Time-out errors with 2 million post migrated vBulletin forum Self-hosting	3	1167	2019年一月4日
Server not response (DO SGP1) Self-hosting	15	2350	2016年五月17日

Discourse 遇到 504 Gateway Time-Out 错误且重建后 CPU 占用 100%

相關主題