# Global messages on 94632 timed out, restarting process, 95535 successfully terminated by \`TERM\` signal

**URL:** <https://meta.discourse.org/t/global-messages-on-94632-timed-out-restarting-process-95535-successfully-terminated-by-term-signal/198794>\
**Category:** Product Support\
**Created:** [August 1, 2021, 3:54am UTC](https://meta.discourse.org/t/global-messages-on-94632-timed-out-restarting-process-95535-successfully-terminated-by-term-signal/198794 "2021-08-01T03:54:33Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)\
**Post date:** [August 1, 2021, 8:56am UTC](https://meta.discourse.org/t/global-messages-on-94632-timed-out-restarting-process-95535-successfully-terminated-by-term-signal/198794/2 "2021-08-01T08:56:51Z")

</div>

Can’t really help, but I think I’ve found the code, in Discourse’s message bus, in function [new\_subscriber\_thread](https://github.com/discourse/message_bus/blob/0d79789b94cc8baabac218ac2ec637e7ade0487d/lib/message_bus.rb#L726):

```plaintext
        if (Time.now - (@last_message || Time.now)) > keepalive_interval * 3
          logger.warn "Global messages on #{Process.pid} timed out, restarting process"
          # No other clean way to remove this thread, its listening on a socket
          # no data is arriving
          #
          # In production we see this kind of situation ... sometimes ... when there is
          # a VRRP failover, or weird networking condition

```

---

_[View the full topic](https://meta.discourse.org/t/global-messages-on-94632-timed-out-restarting-process-95535-successfully-terminated-by-term-signal/198794)._