# Debugging discourse downtime

**URL:** <https://meta.discourse.org/t/debugging-discourse-downtime/72618>\
**Category:** Product Support\
**Created:** [October 23, 2017, 5:09pm UTC](https://meta.discourse.org/t/debugging-discourse-downtime/72618 "2017-10-23T17:09:32Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)\
**Post date:** [October 23, 2017, 8:53pm UTC](https://meta.discourse.org/t/debugging-discourse-downtime/72618/3 "2017-10-23T20:53:07Z")

</div>

Did the server reboot? (check `uptime`)

Did any messages get posted in the kernel logs? (check `dmesg`)

Any relevant entries in syslog? (`less /var/log/syslog`)

The stack traces seem to be a symptom of your downtime, I suspect you lost your networking for the duration of the outage:

```plaintext
/usr/local/lib/ruby/2.3.0/net/smtp.rb:542:in `initialize'
/usr/local/lib/ruby/2.3.0/net/smtp.rb:542:in `open'
/usr/local/lib/ruby/2.3.0/net/smtp.rb:542:in `tcp_socket'
...

```

---

_[View the full topic](https://meta.discourse.org/t/debugging-discourse-downtime/72618)._