MySQL InnoDB crash

Posté le mercredi 28 mai 2008, à 18:00 UTC

Well, we managed to corrupt the InnoDB MySQL storage engine files while cleaning user databases.We set up in production the backup of the last night.

By the way, this is normally not our job to clean the spams in your databases, but we have to do that because we cannot afford the load of billions of spams, so if you don't want that we need to handle the files used by MySQL or PostgreSQL, clean them. In our opinion, this is the time to think to switch to something that don't break, switch to PostgreSQL.

Edit: Well, we had to restore from databases dumps this night in order to fix the corrupted InnoDB database. The records of yesterday are of course lost, but the coherency is assured, which is the most important thing. Everything is good for now.

Upgrade of ssh and ssl keys

Posté le mercredi 14 mai 2008, à 20:00 UTC

Hi,

Due to a security issue with openssl, we have changed all SSL keys.

If you are using a ssh key to log in to our servers, please renew your key and destroy the old key ASAP.

Here is a summary of the new keys fingerprints':

Optical fibers cut

Posté le mercredi 14 mai 2008, à 10:52 UTC

Well, the optical fibers connecting the datacenter where we are hosted were cut by some work on the public road...

A cut of an optical fiber shouldn't be that bad, but it was on a short length where all fibers are, so all the fibers were cut in once.

The fibers are currently being soldered, but this will probably take several hours.

But, the secondary services (ns2 and mx2) are up and running ;)

Please bear with us.

Edit: Soldering done, everything is back online.