Rhododendron

Alright same issue as before, we used the default kernel config that the host supplied to compile the kernel on the website machine. It worked without issue! We applied the same process towards the database machine, and it crashed upon connection. It disabled complete connection to the machine and crashed out all other clients using that machine. Essentially we were dead in the water and were waiting for it to be fixed for HOURS. Once it was fixed and we were able to connect again, we did the EXACT SAME THING as we did to the website machine AGAIN, and it worked. In response to this, we are going to be setting up a MySQL replication server and binding it together with a TCP balancer. So if one server goes down, all traffic can be sent to the other without issue :) Sorry about the downtime.

Alright the downtime was NOT an April Fools joke. Here is what happened. - At around 4AM EST, our machine crashed. An emergency Xen Hypervisor update was installed on the machine and it was brought online. - Our VPS never started, and had issues mounting the disk. - It was determined that the VPS kernel did not properly support the newest version of the Xen Hypervisor, so we downgraded it and the VPS was able to start again. - Main VPS had kernel updated to the latest stable release. - MySQL server refused to start, and after viewing the logs, major corruption was responsible for the server being unable to start. - Quickly restored backups of the MySQL databases, and rebuilt the InnoDB logs, bringing the server back online. Sorry about the downtime. I promise it wasn't my fault!