just had all of my wordops sites give this error this morning, and im not sure why
logging into the terminal I see that mysqld is pegged at 100%, but im not sure why.
i've already tried rebooting the vps. will retry again but I don't know what else to try
have restored my backups (taken from last night) onto a newly spun up VPS
this gets my sites back online, but I'm still curious about what happened, and how to troubleshoot/resolve the issue (before I destroy the old vps instance)
so this is the response I was given by my host provider. It seems they had to restart the node (to resolve some issue they were experiencing)
Your VPS internal errors are a different matter. Most likely disk writes were in flight (queued), or uncommitted and held in RAM, when the node was rebooted. If the writes are not journaled or otherwise integrity checked, then it can cause the underlying file / database / whatever data store to become stuck in an inconsistent/corrupt data. In this case, it sounds like your database needs consistency checks or a rollback to an earlier state. (Not all databases are ACID, guarantee consistency, or have the tools/techniques to do this.)
Is that something that is possible to do with WordOps? I'm already done moving my sites over to the new VPS instance, but would be interested in knowing of such a way in case this happens again in the future.
Hosted by VirtuBox