# 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:** 4

<div class="post-metadata">

**Author:** ![jphaas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jphaas/32/120601_2.png) [@jphaas](https://meta.discourse.org/u/jphaas)\
**Post date:** [October 24, 2017, 2:53pm UTC](https://meta.discourse.org/t/debugging-discourse-downtime/72618/4 "2017-10-24T14:53:46Z")

</div>

Thanks guys!

System did not reboot (uptime 218 days). Unfortunately it looks like syslog and dmesg aren’t configured on my box to retain logs more than a day, so I don’t see anything from around then.

I do see a lot of messages (every 10 minutes or so), still ongoing, like this:

```
Oct 24 10:35:03 forum kernel: [18839676.542030] type=1400 audit(1508855703.196:112881): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=27630 comm="ps" requested_mask="trace" denied_mask="trace" peer="docker-default

```

Not sure how that would be related, though.

Anyway, if it happens again, I know now to check syslog + dmesg right after the incident – I appreciate the help.

---

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