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

**URL:** https://meta.discourse.org/t/discourse-stuck-with-504-gateway-time-out-error-and-100-cpu-after-rebuild/395794
**Category:** Support
**Tags:** server-resources
**Created:** [2026 年 2 月 11 日午後 1:29 UTC](https://meta.discourse.org/t/discourse-stuck-with-504-gateway-time-out-error-and-100-cpu-after-rebuild/395794 "2026-02-11T13:29:37Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![loic](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/loic/32/105621_2.png) [@loic](https://meta.discourse.org/u/loic)
#### Post date: [2026 年 2 月 11 日午後 2:28 UTC](https://meta.discourse.org/t/discourse-stuck-with-504-gateway-time-out-error-and-100-cpu-after-rebuild/395794/7 "2026-02-11T14:28:43Z")

</div>

修正すべき変更をマージしました。

> <https://github.com/discourse/discourse/commit/7324b327cdf72c2e468d33ce35074f5d1c78fe6f>
>
> 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` に反映されるはずですので、修正が利用可能になったらドロッパーを更新してみてください。

---

_[View the full topic](https://meta.discourse.org/t/discourse-stuck-with-504-gateway-time-out-error-and-100-cpu-after-rebuild/395794)._