# Stuck after reboot frequently

**URL:** <https://forums.suse.com/t/stuck-after-reboot-frequently/16485>\
**Category:** RancherOS\
**Created:** [February 3, 2020, 3:53pm UTC](https://forums.suse.com/t/stuck-after-reboot-frequently/16485 "2020-02-03T15:53:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![pnelson](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/pnelson/32/5944_2.png) [@pnelson](https://forums.suse.com/u/pnelson)\
**Post date:** [February 3, 2020, 3:53pm UTC](https://forums.suse.com/t/stuck-after-reboot-frequently/16485/1 "2020-02-03T15:53:52Z")

</div>

In this particular case I did a no-op upgrade from 1.5.5 not realizing I was already upgraded but proceeded with the reboot anyway.

It rebooted fine but I noticed my user containers weren’t started and `docker ps -a` just hung. I tried `sudo system-docker restart docker` and that didn’t help either. The issue resolved itself over the next 10 or so minutes and now the daemon magically responds.

I’ve bumped into similar issues a few times now. Actually, almost every time I’ve done an upgrade or even reboot without upgrading. Sometimes it is system-docker that gets stuck, so I can’t even SSH in for about 10 minutes or so til it decides to work. It’s usually faster to provision a new machine.

Is there anything I can do to help diagnose this? Has anyone else experienced this?
