I have a recently new build, started on 6.4.1 and upgraded yesterday to 6.5.0.  Everything seemed to be going fine...I had just installed the UpStatsBoard docker just to check it out, but then removed it.  I went to my CA Cleanup plugin and it just spun and spun and wouldnt do anything.  I noticed the same thing when going into Community Apps and Docker.  Nothing came up at all, so I figured I'd try stopping the array and rebooting.  Powered down my VMs, hit stop array and it was just stuck at "stopping array".  I was able to SSH in and found some posts about looking for open tasks, so I ran the commands and killed some tasks.  Nothing seemed to work.  Finally ran the powerdown command and my physical server is still up, I can ping my IP and still have the SSH session, but can no longer access the GUI.  At this point, is my only option really to hard shut down and power back on?  What can I do to troubleshoot/avoid this again?

I have the exact same behavior. 

I had to cold start the server. 

On 2018-03-28 at 9:35 PM, bonzovt said:

What can I do to troubleshoot/avoid this again?

You should try upgrading to 6.5.1-rc3  Should fix up the problem with the docker subsystem hanging up for the odd user.

did upgrade to 6.5.1-rc3, things have been pretty stable, although i haven't been messing with containers or changing things around much recently.  everything came up fine after the hard reset.  i did cross my fingers and toes until then.  community apps plugin also working great again.  thanks!