# Upgrade failed due to process terminating

**URL:** <https://meta.discourse.org/t/upgrade-failed-due-to-process-terminating/33646>\
**Category:** Self-hosting\
**Created:** [9월 23, 2015, 3:52오후 UTC](https://meta.discourse.org/t/upgrade-failed-due-to-process-terminating/33646 "2015-09-23T15:52:36Z")\
**Posts on this page:** 1\
**Showing post:** 23

<div class="post-metadata">

**Author:** ![Noya](https://avatars.discourse-cdn.com/v4/letter/n/ccd318/32.png) [@Noya](https://meta.discourse.org/u/Noya)\
**Post date:** [9월 28, 2015, 12:10오후 UTC](https://meta.discourse.org/t/upgrade-failed-due-to-process-terminating/33646/23 "2015-09-28T12:10:00Z")

</div>

Hey everyone!

I’ve been struggling with the exact same problem as @shadowhand since my first steps with Discourse a few weeks ago. For me, it is still not resolved on current beta.

After having a look at `message_bus.rb`, I think the problem is as follows: The default `keepalive_interval` is set to `60` seconds and the subscriber is killed after 3x this interval, i.e. after ~ 3 minutes. The asset precompilation for some files takes about 5 minutes on my DigitalOcean droplet.

Without having further investigated the asset compilation step, my guess would be that while a single asset is compiling, the subscriber is blocked, can’t respond to the keepalive and… gets killed mercilessly 😉 .

To confirm this, I’ve set the default `keepalive_interval` to `0`, which disables the keepalive mechanism. Asset precompilation then runs through as expected 😄 .

Maybe a solution would be to disable or raise the `keepalive_interval` for the asset precompilation step? Anyway, hope this will help you to fix this bug.

PS: Thank you for your awesome work on Discourse!

---

_[View the full topic](https://meta.discourse.org/t/upgrade-failed-due-to-process-terminating/33646)._