# Nameko behavior on rabbitmq crash

**URL:** <https://discourse.nameko.io/t/nameko-behavior-on-rabbitmq-crash/336>\
**Category:** googlegroup\
**Created:** [August 30, 2018, 11:19pm UTC](https://discourse.nameko.io/t/nameko-behavior-on-rabbitmq-crash/336 "2018-08-30T23:19:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rizplate](https://avatars.discourse-cdn.com/v4/letter/r/43a26b/32.png) [@rizplate](https://discourse.nameko.io/u/rizplate)\
**Post date:** [August 30, 2018, 11:19pm UTC](https://discourse.nameko.io/t/nameko-behavior-on-rabbitmq-crash/336/1 "2018-08-30T23:19:53Z")

</div>

What will happen if the rabbitmq crashes, will nameko reconnect after rabbitmq comes up?.  
we are seeing that with only 4-5 services and low load i.e. 4 msg/sec , rabbitmq inside a docker , is crashing and when rabbitmq crashes, all services stops or get hung

i.e. we are seeing behavior similar to this [https://groups.google.com/forum/?nomobile=true#!msg/nameko-dev/POBxAV71TUE/XRqyV-iHCwAJ](https://groups.google.com/forum/?nomobile=true#!msg/nameko-dev/POBxAV71TUE/XRqyV-iHCwAJ)

---

<div class="post-metadata">

**Author:** ![mattbennett](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.nameko.io/mattbennett/32/13_2.png) [@mattbennett](https://discourse.nameko.io/u/mattbennett)\
**Post date:** [September 3, 2018, 10:46am UTC](https://discourse.nameko.io/t/nameko-behavior-on-rabbitmq-crash/336/2 "2018-09-03T10:46:31Z")

</div>

> What will happen if the rabbitmq crashes, will nameko reconnect after rabbitmq comes up?

Yes. As long as the process stays up, the consumers should attempt to reconnect.

> we are seeing behavior similar to this [https://groups.google.com/forum/?nomobile=true#!msg/nameko-dev/POBxAV71TUE/XRqyV-iHCwAJ](https://groups.google.com/forum/?nomobile=true#!msg/nameko-dev/POBxAV71TUE/XRqyV-iHCwAJ)

Hanging and crashing would mean very different causes. If you see the process terminate with a crash, you may be experiencing the above. It very specifically happens when an exception occurs inside `get_dependency`. This is a “feature” that we could easily remove, and is also easily worked-around by running Nameko under a process manager like supervisord.

Please post a stacktrace or otherwise describe the “hang” in more detail.
