Mysql service start failed

Hello !

I’m having some trouble with my percona server,
When I start the service it says : failed !
But the server is running ank working, and there is nothing in the log files that looks like an error.

#service mysql startStarting MySQL (Percona Server) database server: mysqld . . . . . . . . . . . . . . failed!

#tail -n 20 /var/log/mysql/mysql-error.log121216 16:30:51 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql/121216 16:30:51 [Note] Plugin ‘FEDERATED’ is disabled.121216 16:30:51 InnoDB: The InnoDB memory heap is disabled121216 16:30:51 InnoDB: Mutexes and rw_locks use GCC atomic builtins121216 16:30:51 InnoDB: Compressed tables use zlib 1.2.3121216 16:30:51 InnoDB: Using Linux native AIO121216 16:30:51 InnoDB: Initializing buffer pool, size = 6.0G121216 16:30:52 InnoDB: Completed initialization of buffer pool121216 16:30:52 InnoDB: highest supported file format is Barracuda.121216 16:30:52 InnoDB: Waiting for the background threads to start121216 16:30:53 Percona XtraDB () 1.1.8-rel29.2 started; log sequence number 119427084121216 16:30:53 [Note] Recovering after a crash using /var/lib/mysql/mysql-bin121216 16:30:53 [Note] Starting crash recovery…121216 16:30:53 [Note] Crash recovery finished.121216 16:30:54 [Note] Server hostname (bind-address): ‘’; port: 3306121216 16:30:54 [Note] - ‘’ resolves to ‘’;121216 16:30:54 [Note] Server socket created on IP: ‘’.121216 16:30:54 [Note] Event Scheduler: Loaded 0 events121216 16:30:54 [Note] /usr/sbin/mysqld: ready for connections.Version: ‘5.5.28-29.2-log’ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 Percona Server (GPL), Release 29.2

#ps aux | grep mysql21340 pts/1 S 0:00 /bin/sh /usr/bin/mysqld_safe21797 pts/1 Sl 0:00 /usr/sbin/mysqld

Im running this server on a debian (squeeze).


Are you able to do normal operation in MySQL like login, running queries etc? If yes, then I guess it’s possible bug. Can you please report this bug with all details here?

There was also the same problem in previous version ( msg_9679) but noone has reported bug I guess.