That doesn't really explain it in much detail or explain why i'm still down after 15 hours, but thanks for taking the time to reply.
What I would ask based on your response is how one of the VPS containers can cause this when the whole idea of containers is to split a physical node into multiple virtual nodes but protect each one so that no single container can impact on the others.
I have had serious ongoing issues for some time on this node and have constantly been told that no other container can be causing the issues I am seeing (john and mark have been made aware of this) due to the way the virtualisation works.
The node appears to have been restarted 3 times in the early hours of this morning and it was the 3rd reboot that appears to have caused my issues.
My container has been down for 15 hours
, Mysql server will not start and stay running which means that plesk won't function, half of my sites won't function as they use Mysql.
My MSSQL2005 databases are running, but the management software won't run as that is corrupt.
And theres a whole load of files that are corrupt and won't fix using a chkdsk /f even during a reboot.
Long and short of it is that I have now requested that the container be restored to 20th Dec 4am backup and thankfully I have some database backups that are more recent that I can apply once it's back up.
And it's now an hour since I gave the go-ahead to do the restore of the container and it still hasn't been shutdown ready for restore
EW52 - whats happened to it ?
Hello
Linear Mode
