init script starts twice when MySQL is doing a crash recovery

Bug #1226653 reported by Jose Arthur Benetasso Villanova
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Incomplete
Undecided
Unassigned

Bug Description

Hi.

I have this situation occurring in my environment:

* MySQL crashes for any reason
* MySQL starts again and begin an InnoDB crash recovery
* Someone starts MySQL using the init script

After this, I have a MySQL process without the engine InnoDB.

What I expected is that MySQL waits the crash recovery finishes and startup with InnoDB engine working.

Tags: pkg
Revision history for this message
Valerii Kravchuk (valerii-kravchuk) wrote :

What exact Percona Server version do you use? This can be something like upstream http://bugs.mysql.com/bug.php?id=61291.

Please, upload also the entire MySQL error log with all the messages related to this situation.

Changed in percona-server:
status: New → Incomplete
Revision history for this message
Jose Arthur Benetasso Villanova (jose-arthur) wrote :

percona-server-server-5.1 5.1.69-rel14.7-572.squeeze

mysqld log:

130918 09:26:56 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql/data
130918 9:26:56 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3.4
130918 9:26:56 InnoDB: Initializing buffer pool, size = 2.7G
130918 9:26:56 InnoDB: Completed initialization of buffer pool
130918 9:26:56 InnoDB: highest supported file format is Barracuda.
130918 09:26:57 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql/data
130918 9:26:58 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3.4
130918 9:26:58 InnoDB: Initializing buffer pool, size = 2.7G
130918 9:26:58 InnoDB: Completed initialization of buffer pool
InnoDB: Unable to lock /var/lib/mysql/data/ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.

How to simulate:

Create databases and tables innodb:

for i in {25..1000}; do mysql -e "create database ze$i;"; for j in {1..1000}; do mysql ze$i -e "create table ze$j (id int primary key auto_increment)engine=innodb;"; mysql ze$i -e "insert into ze$j values (default), (default), (default), (default), (default)"; done; done

kill -9 mysqld mysqld_safe processes

from 2 different shells:

/etc/init.d/mysql start

tags: added: pkg
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3025

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.