# CPUのスパイクがサーバーのクラッシュを引き起こしているようです

**URL:** <https://meta.discourse.org/t/cpu-spikes-seem-to-be-crashing-our-server/64901>\
**Category:** Self-hosting\
**Tags:** server-resources\
**Created:** [2017 年 6 月 21 日午後 4:11 UTC](https://meta.discourse.org/t/cpu-spikes-seem-to-be-crashing-our-server/64901 "2017-06-21T16:11:39Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![ossia](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ossia/32/215651_2.png) [@ossia](https://meta.discourse.org/u/ossia)\
**Post date:** [2017 年 6 月 21 日午後 4:11 UTC](https://meta.discourse.org/t/cpu-spikes-seem-to-be-crashing-our-server/64901/1 "2017-06-21T16:11:39Z")

</div>

Over the past 10 days or so - both before and after updating Discourse to the latest version - our server has crashed once every day or two. This morning it crashed twice in quick succession.

We’ve been too busy to stop and investigate, and have just been power cycling it, but now it’s clearly worth reaching out to you all about it.

CPU seems to have inexplicably spiked several times before the crash:

 ![](https://global.discourse-cdn.com/meta/original/3X/d/e/deb8cd85f2f5db5d2839dff73483f084f60f3c45.png)

Memory dropping to zero was due to the reboot. Also note that our backups happen at night, so this doesn’t seem to be related to a database backup.

We are running currently running the 4gb ram Digital Ocean droplet and would prefer not to go up to the next tier since it would double our monthly cost. Here are the stats:

 ![](https://global.discourse-cdn.com/meta/original/3X/c/d/cd3971c520bbd835cc9504d4cc740f312373830a.png)

Digital Ocean is reporting no issues on their status page:

 ![](https://global.discourse-cdn.com/meta/original/3X/7/3/7378983de60ef4d7e8fcec40a9f9299a58006d48.png)

Do you all have any ideas what might be causing this, or what we should do about it?

---

_[View the full topic](https://meta.discourse.org/t/cpu-spikes-seem-to-be-crashing-our-server/64901)._