OpenVZ Forum


Home » General » Support » OPENVZ / MYSQL CRASH RADOMLY ON CONTAINER
OPENVZ / MYSQL CRASH RADOMLY ON CONTAINER [message #51343] Wed, 23 April 2014 14:28 Go to previous message
jerem is currently offline  jerem
Messages: 4
Registered: April 2014
Junior Member
Sorry for my english ...

We have about 29 virtual machines with open vz.
Ramdomly mysql crash with following errors in container mysql-error log file :

Version: '5.1.63-0+squeeze1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
Killed
140423 11:21:37 mysqld_safe Number of processes running now: 0
140423 11:21:37 mysqld_safe mysqld restarted
140423 11:21:37 [Note] Plugin 'FEDERATED' is disabled.
140423 11:21:37 InnoDB: Initializing buffer pool, size = 8.0M
140423 11:21:37 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140423 11:21:37 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Last MySQL binlog file position 0 5545605, file name /var/log/mysql/mysql-bin.000002
140423 11:21:38 InnoDB: Started; log sequence number 0 1903177976
140423 11:21:38 [Note] Recovering after a crash using /var/log/mysql/mysql-bin
140423 11:21:38 [Note] Starting crash recovery...
140423 11:21:38 [Note] Crash recovery finished.
140423 11:21:38 [Note] Event Scheduler: Loaded 0 events
140423 11:21:38 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.63-0+squeeze1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
Killed
140423 11:21:38 mysqld_safe Number of processes running now: 0
140423 11:21:38 mysqld_safe mysqld restarted
140423 11:21:38 [Note] Plugin 'FEDERATED' is disabled.
140423 11:21:38 InnoDB: Initializing buffer pool, size = 8.0M
140423 11:21:38 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140423 11:21:38 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Last MySQL binlog file position 0 5545605, file name /var/log/mysql/mysql-bin.000002
140423 11:21:38 InnoDB: Started; log sequence number 0 1903177976
140423 11:21:38 [Note] Recovering after a crash using /var/log/mysql/mysql-bin
140423 11:21:38 [Note] Starting crash recovery...
140423 11:21:38 [Note] Crash recovery finished.
140423 11:21:38 [Note] Event Scheduler: Loaded 0 events
140423 11:21:38 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.63-0+squeeze1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
Killed
140423 11:21:38 mysqld_safe Number of processes running now: 0
140423 11:21:38 mysqld_safe mysqld restarted
140423 11:21:38 [Note] Plugin 'FEDERATED' is disabled.
140423 11:21:38 InnoDB: Initializing buffer pool, size = 8.0M
140423 11:21:38 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140423 11:21:38 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
Killed
140423 11:21:38 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Space on boot
Next Topic: RHEL 6 Container does not properly start on CentOS 5 host
Goto Forum:
  


Current Time: Sun Aug 03 09:26:12 GMT 2025

Total time taken to generate the page: 1.40576 seconds