Po zalogowaniu do konsoli zacząłem sprawdzać. Po dodaniu do pliku my.cnf innodb_force_recovery = 2 serwera ruszył, odpala się phpmyadmin i wydaje się, że jest ok. Ale zakładam, że serwer powinien się odpalać bez tego wpisu a się nie odpala...
Co zrobiłem
1. Boot serwera + reset mysl i sprawdzenie
2. Po dodaniu wpisu do my.cnf: naprawa tabel przez phpmyadmin + reset mysql i sprawdzenie
3. Wywalenie wszystkich tabel z silnikiem InnoDb + reset mysql i sprawdzenie
Log z /var/log/mysql/error.log :
140411 23:33:56 [Note] Plugin 'FEDERATED' is disabled.
140411 23:33:56 InnoDB: The InnoDB memory heap is disabled
140411 23:33:56 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140411 23:33:56 InnoDB: Compressed tables use zlib 1.2.3.4
140411 23:33:56 InnoDB: Initializing buffer pool, size = 128.0M
140411 23:33:56 InnoDB: Completed initialization of buffer pool
140411 23:33:56 InnoDB: highest supported file format is Barracuda.
140411 23:33:56 InnoDB: Waiting for the background threads to start
140411 23:33:57 InnoDB: 5.5.32 started; log sequence number 2776373463
140411 23:33:57 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
140411 23:33:57 [Note] - '127.0.0.1' resolves to '127.0.0.1';
140411 23:33:57 [Note] Server socket created on IP: '127.0.0.1'.
140411 23:33:57 InnoDB: Assertion failure in thread 2728844096 in file trx0purge.c line 840
InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/ ... overy.html
InnoDB: about forcing recovery.
"error.log" 285L, 14855C