Le serveur est en cours de redémarrage suite à un incident technique.
Update(s):
Date: 2009-09-25 08:48:11 UTC le serveur est à nouveau opérationnel
Date: 2009-09-25 08:45:48 UTC Le crash a été provoqué par une défaillance du moteur innoDB.
Le moteur a lancé un rollback automatique, donc il est possible que certaines bases de données utilisant innoDB aient perdu quelques enregistrements :
InnoDB: Starting in background the rollback of uncommitted transactions
090925 10:42:19 InnoDB: Rolling back trx with id 0 453985122, 1 rows to undo
090925 10:42:19 InnoDB: Started; log sequence number 6 3559807333
InnoDB: Rolling back of trx id 0 453985122 completed
090925 10:42:19 InnoDB: Rolling back trx with id 0 453985034, 1 rows to undo
InnoDB: Rolling back of trx id 0 453985034 completed
090925 10:42:19 InnoDB: Rolling back trx with id 0 453984867, 1 rows to undo
InnoDB: Rolling back of trx id 0 453984867 completed
090925 10:42:19 InnoDB: Rolling back trx with id 0 453984854, 1 rows to undo
InnoDB: Rolling back of trx id 0 453984854 completed
090925 10:42:19 InnoDB: Rolling back trx with id 0 453984832, 1 rows to undo
InnoDB: Rolling back of trx id 0 453984832 completed
090925 10:42:19 InnoDB: Rolling back trx with id 0 453984621, 1 rows to undo
InnoDB: Rolling back of trx id 0 453984621 completed
Posted Sep 25, 2009 - 08:42 UTC
This incident affected: Web Hosting || Datacenter GRA (Cluster002, Cluster003, Cluster006, Cluster007, Cluster011, Cluster012, Cluster013, Cluster014, Cluster015, Cluster017, Cluster020, Cluster021, Cluster023, Cluster024, Cluster025, Cluster026, Cluster027, Cluster028, Cluster029, Cluster030, Cluster031).