Upgraded from 6.5.3 to 6.6.7 and could not start any services


Recommended Posts

I upgraded from 6.5.3 to 6.6.7, and now the docker and vm manager are not responding.

When I enabled docker, I get Docker service failed to start error. The vm manager just keeps spinning.

The server has been up for over 30 minutes now, and two of the cores still at 100% (showing in the dashboard)

I could not cd to my cache, but it doesn't say that it is "unmountable"

I could not open the log after clicking it

I think I found what causing some of the CPU cores to load at 100% - the parity check. No matter what I do, the parity check keeps running. If I disable it before turning on the array, then enable docker then the damn parity would start running again.

It has been 7 hours now for the parity check, but the docker is still in Starting services. And could not get the diagnostic file. 

 

I have never had luck upgrading my server. Should I go back to 6.5.3 and stay with it?

 

See screenshot for core utilization

 

Screenshot 2019-03-18 at 04.51.49.png

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.