At 6:48am Central Time our game server decided to restart the MySQL server to complete the automated installation of a patch. This patch provided a security update.
Unfortunately a change I made months ago kicked into effect. This change increased the InnoDB database storage engine's log size from the default 5MB to 1GB. Since the log files already existed the database engine didn't know how to handle the file size change and refused to load the database handler needed to read InnoDB databases. Most programmers know that TrinityCore uses InnoDB for its superior transaction handling and speed.
Once this change affected the realms, it also affected the website. Don't worry, your characters did NOT go poof.
At about 7am I received a phone call from our Staff Manager 'Mattmeck'. He informed me of the issue. As of 7:12am Central Time the MySQL server was fixed and the realms were booting back up. All realms should be back online at this time.
Let me make sure to make this clear: No data was lost. The server did what it was supposed to do and protected itsself from data corruption.
TL;DR - MySQL server crapped its pants because of human error. Human error fixed and stuff is back online in a total time of about 30 minutes.
We apologize for the unscheduled downtime.













