InnoDB trouble again :-(
Slowly getting tired of this new feature, it breaks to many websites.
Until last night everything was running fine, this morning I got flooded with emails about high load and of course almost anything what uses mysql was broken because mysql was gone away... broken somehow.
After several attempts, I got mysql up and running again, but now it won't display or uses any InnoDB tables.
Anyone any suggestions???
This is the content of /etc/my.cnf
[mysqld]
innodb_file_per_table=1
local-infile=0
#
character-set-server=utf8
collation-server=utf8_general_ci
#
default-storage-engine=MYISAM
#
open_files_limit=3308
#
[client]
default-character-set=utf8
#
Database server
Server: Localhost via UNIX socket
Server type: MySQL
Server version: 5.5.35-cll - MySQL Community Server (GPL)
Protocol version: 10
User: [email protected]
Server charset: UTF-8 Unicode (utf8)
Web server
cpsrvd 11.40.1.11
Database client version: libmysql - 5.0.96
PHP extension: mysqli Documentation
phpMyAdmin
Version information: 4.0.8, latest stable version: 4.1.8, latest stable version: 4.1.8
mysql> SHOW ENGINES;
+--------------------+---------+----------------------------------------------------------------+--------------+------+------------+
| Engine | Support | Comment | Transactions | XA | Savepoints |
+--------------------+---------+----------------------------------------------------------------+--------------+------+------------+
| MyISAM | DEFAULT | MyISAM storage engine | NO | NO | NO |
| MRG_MYISAM | YES | Collection of identical MyISAM tables | NO | NO | NO |
| CSV | YES | CSV storage engine | NO | NO | NO |
| BLACKHOLE | YES | /dev/null storage engine (anything you write to it disappears) | NO | NO | NO |
| MEMORY | YES | Hash based, stored in memory, useful for temporary tables | NO | NO | NO |
| PERFORMANCE_SCHEMA | YES | Performance Schema | NO | NO | NO |
| ARCHIVE | YES | Archive storage engine | NO | NO | NO |
| FEDERATED | NO | Federated MySQL storage engine | NULL | NULL | NULL |
| InnoDB | YES | Supports transactions, row-level locking, and foreign keys | YES | YES | YES |
+--------------------+---------+----------------------------------------------------------------+--------------+------+------------+
9 rows in set (0.00 sec)
More info:
It seems the server run out of memory: Swap Used 0.42% (17,196 of 4,128,760)
InnoDB uses memory as a default and crashed, but no autorecover is done.
https://dev.mysql.com/doc/refman/5.6/en/innodb-default-se.html
If your server crashes because of a hardware or software issue, regardless of what was happening in the database at the time, you don't need to do anything special after restarting the database. InnoDB crash recovery automatically finalizes any changes that were committed before the time of the crash, and undoes any changes that were in process but not committed. Just restart and continue where you left off. This process is now much faster than in MySQL 5.1 and earlier.
Slowly getting tired of this new feature, it breaks to many websites.
Until last night everything was running fine, this morning I got flooded with emails about high load and of course almost anything what uses mysql was broken because mysql was gone away... broken somehow.
After several attempts, I got mysql up and running again, but now it won't display or uses any InnoDB tables.
Anyone any suggestions???
This is the content of /etc/my.cnf
[mysqld]
innodb_file_per_table=1
local-infile=0
#
character-set-server=utf8
collation-server=utf8_general_ci
#
default-storage-engine=MYISAM
#
open_files_limit=3308
#
[client]
default-character-set=utf8
#
Database server
Server: Localhost via UNIX socket
Server type: MySQL
Server version: 5.5.35-cll - MySQL Community Server (GPL)
Protocol version: 10
User: [email protected]
Server charset: UTF-8 Unicode (utf8)
Web server
cpsrvd 11.40.1.11
Database client version: libmysql - 5.0.96
PHP extension: mysqli Documentation
phpMyAdmin
Version information: 4.0.8, latest stable version: 4.1.8, latest stable version: 4.1.8
mysql> SHOW ENGINES;
+--------------------+---------+----------------------------------------------------------------+--------------+------+------------+
| Engine | Support | Comment | Transactions | XA | Savepoints |
+--------------------+---------+----------------------------------------------------------------+--------------+------+------------+
| MyISAM | DEFAULT | MyISAM storage engine | NO | NO | NO |
| MRG_MYISAM | YES | Collection of identical MyISAM tables | NO | NO | NO |
| CSV | YES | CSV storage engine | NO | NO | NO |
| BLACKHOLE | YES | /dev/null storage engine (anything you write to it disappears) | NO | NO | NO |
| MEMORY | YES | Hash based, stored in memory, useful for temporary tables | NO | NO | NO |
| PERFORMANCE_SCHEMA | YES | Performance Schema | NO | NO | NO |
| ARCHIVE | YES | Archive storage engine | NO | NO | NO |
| FEDERATED | NO | Federated MySQL storage engine | NULL | NULL | NULL |
| InnoDB | YES | Supports transactions, row-level locking, and foreign keys | YES | YES | YES |
+--------------------+---------+----------------------------------------------------------------+--------------+------+------------+
9 rows in set (0.00 sec)
More info:
It seems the server run out of memory: Swap Used 0.42% (17,196 of 4,128,760)
InnoDB uses memory as a default and crashed, but no autorecover is done.
https://dev.mysql.com/doc/refman/5.6/en/innodb-default-se.html
If your server crashes because of a hardware or software issue, regardless of what was happening in the database at the time, you don't need to do anything special after restarting the database. InnoDB crash recovery automatically finalizes any changes that were committed before the time of the crash, and undoes any changes that were in process but not committed. Just restart and continue where you left off. This process is now much faster than in MySQL 5.1 and earlier.
Last edited: