재구축 후 Discourse가 504 Gateway Time-Out 오류와 100% CPU 사용률로 멈춤

loic · 2월 11, 2026, 2: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에 곧 반영될 예정이니, 수정 사항이 사용 가능해지면 드롭릿을 업데이트해 보실 수 있을까요?

글		댓글	조회수
Emergency help - freeCodeCamp Discourse down Self-hosting	18	2404	2월 22, 2017
Discourse stopping working - CPU/RAM load? Support	7	1162	9월 8, 2019
CPU, Memory and Swap at 100% Self-hosting server-resources	6	734	11월 8, 2021
504 Gateway Time-out errors with 2 million post migrated vBulletin forum Self-hosting	3	1155	1월 4, 2019
Server not response (DO SGP1) Self-hosting	15	2332	5월 17, 2016

재구축 후 Discourse가 504 Gateway Time-Out 오류와 100% CPU 사용률로 멈춤

Related topics