# Upgrade failed due to process terminating

**URL:** <https://meta.discourse.org/t/upgrade-failed-due-to-process-terminating/33646>\
**Category:** Self-hosting\
**Created:** [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:** 14

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [24 سبتمبر 2015، 10:39ص UTC](https://meta.discourse.org/t/upgrade-failed-due-to-process-terminating/33646/14 "2015-09-24T10:39:46Z")

</div>

Getting `SIGTERM` is a real curiosity. Ctrl-C sends `SIGINT`, and the OOM killer sends `SIGKILL`. `SIGTERM` is the default signal sent by the `kill` command, if you don’t specify a different signal.

Looking at the `message_bus` code, I’m about 99% sure the problem is _something_ to do with the communication being interrupted and the message bus deciding to take its bat and ball and go home. The exception coming out of `message_bus` shouldn’t happen, either (I’ll do a PR on that), but it’s a side-effect, not the cause. @sam is obviously the go-to guy on what’s going on in the innards, it being his gem.

---

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