# Solo node became unresponsive and required reboot

**URL:** <https://forum.datomic.com/t/solo-node-became-unresponsive-and-required-reboot/976>\
**Category:** Troubleshooting\
**Created:** [May 8, 2019, 7:50am UTC](https://forum.datomic.com/t/solo-node-became-unresponsive-and-required-reboot/976 "2019-05-08T07:50:30Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![max](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.datomic.com/max/32/298_2.png) [@max](https://forum.datomic.com/u/max)\
**Post date:** [May 8, 2019, 7:50am UTC](https://forum.datomic.com/t/solo-node-became-unresponsive-and-required-reboot/976/1 "2019-05-08T07:50:31Z")

</div>

Last week I couldn’t connect to datomic through the bastion and the lambdas timed out. The cloud watch had no new events, and the instance system log had no strangeness as far as I could tell. The EC2 health checks all indicated that everything was ok.

I did a reboot on the instance and had to wait 4 minutes which likely meant that EC2 had to do a forced reboot. When it came up again everything was working as normal.

Have you seen similar issues? Is there a good way to handle it? Can I monitor the Datomic instance in a way that catches errors like this?

---

<div class="post-metadata">

**Author:** ![marshall](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.datomic.com/marshall/32/48_2.png) [@marshall](https://forum.datomic.com/u/marshall)\
**Post date:** [May 28, 2019, 3:25pm UTC](https://forum.datomic.com/t/solo-node-became-unresponsive-and-required-reboot/976/2 "2019-05-28T15:25:40Z")

</div>

Max,

We have seen a couple of issues that could explain this behavior. They have been corrected in the latest release of Datomic Cloud: [https://docs.datomic.com/cloud/releases.html#477-8741](https://docs.datomic.com/cloud/releases.html#477-8741)

If you upgrade to the latest version and see this behavior again, please let us know and we can look into the logs/system details to determine what might be the underlying cause.

-Marshall

---

<div class="post-metadata">

**Author:** ![max](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.datomic.com/max/32/298_2.png) [@max](https://forum.datomic.com/u/max)\
**Post date:** [November 25, 2019, 7:55am UTC](https://forum.datomic.com/t/solo-node-became-unresponsive-and-required-reboot/976/3 "2019-11-25T07:55:19Z")

</div>

Today this happened again. The log became completely silent Friday night and I had to reboot to solo node be able to connect again. We’re just about to upgrade to the production topology. I would be happy if you could have a look. What do you need?

---

<div class="post-metadata">

**Author:** ![marshall](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.datomic.com/marshall/32/48_2.png) [@marshall](https://forum.datomic.com/u/marshall)\
**Post date:** [December 11, 2019, 3:26pm UTC](https://forum.datomic.com/t/solo-node-became-unresponsive-and-required-reboot/976/4 "2019-12-11T15:26:47Z")

</div>

Max,

You can file a support ticket at [support.cognitect.com](http://support.cognitect.com) and we can help investigate.