OpenVZ Forum: Support » OPENVZ / MYSQL CRASH RADOMLY ON CONTAINER

Home » General » Support » OPENVZ / MYSQL CRASH RADOMLY ON CONTAINER

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

OPENVZ / MYSQL CRASH RADOMLY ON CONTAINER [message #51343]

Wed, 23 April 2014 14:28

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

Report message to a moderator

Re: mysql crash radomly on container [message #51344 is a reply to message #51343]

Wed, 23 April 2014 17:18

curx
Messages: 739
Registered: February 2006
Location: Nürnberg, Germany

Senior Member

Hi,

have you seen any failcounter in your UBC, or any OOM Killers?

For more info see https://wiki.openvz.org/Resource_shortage

Bye,
Thorsten

Report message to a moderator

Re: mysql crash radomly on container [message #51346 is a reply to message #51344]

Thu, 24 April 2014 07:29

jerem
Messages: 4
Registered: April 2014

Junior Member

Hi,

Thnx for your reply.

What can i do with this result ? Shocked

Best regards,

Attachment: Capture d’écran 2014-04-24 à 09.36.02.png
(Size: 66.74KB, Downloaded 360 times)

[Updated on: Thu, 24 April 2014 07:38]

Report message to a moderator

Re: mysql crash radomly on container [message #51347 is a reply to message #51346]

Thu, 24 April 2014 07:39

jerem
Messages: 4
Registered: April 2014

Junior Member

I try to increase memory limit to 2 Go.

It seems mysql take about 600 Mo of memory resource ... Is it normal ?

root@dev:~# ps aux | sort -nk +4 | tail
root 268 0.0 0.4 99632 8876 ? Ss 09:34 0:00 /usr/sbin/apache2 -k start
www-data 469 0.0 0.5 101384 11820 ? S 09:37 0:00 /usr/sbin/apache2 -k start
www-data 470 0.0 0.5 101384 11820 ? S 09:37 0:00 /usr/sbin/apache2 -k start
root 382 0.0 0.6 17276 13064 ? Ss 09:34 0:00 /usr/bin/perl /usr/share/webmin/miniserv.pl /etc/webmin/miniserv.conf
www-data 296 0.0 0.6 101672 12940 ? S 09:34 0:00 /usr/sbin/apache2 -k start
www-data 466 0.0 0.6 101672 12892 ? S 09:37 0:00 /usr/sbin/apache2 -k start
www-data 295 0.0 0.9 106792 19928 ? S 09:34 0:00 /usr/sbin/apache2 -k start
www-data 297 0.0 1.4 104868 30728 ? S 09:34 0:00 /usr/sbin/apache2 -k start
mysql 650 0.3 2.9 633104 60820 pts/0 Sl 09:37 0:00 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --log-error=/var/log/mysql/mysql-error.log --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock --port=3306
www-data 300 0.1 3.4 129912 72176 ? S 09:34 0:00 /usr/sbin/apache2 -k start

Thnx.

[Updated on: Thu, 24 April 2014 07:40]

Report message to a moderator