Bug #69058 Assertion failure in file srv0srv.c line 2910
Submitted: 24 Apr 2013 19:44 Modified: 29 Apr 2013 10:06
Reporter: Greg Hazel Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S1 (Critical)
Version:5.5.30 OS:Linux
Assigned to: CPU Architecture:Any

[24 Apr 2013 19:44] Greg Hazel
Our mysql server crashes periodically and restarts. This causes unwanted downtime and disk IO, and also tends to break the slave replication.

InnoDB: ###### Diagnostic info printed to the standard error stream
InnoDB: Error: semaphore wait has lasted > 600 seconds
InnoDB: We intentionally crash the server, because it appears to be hung.
130424 19:27:18  InnoDB: Assertion failure in thread 140027430221568 in file srv0srv.c line 2910
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
19:27:18 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary 
or one of the libraries it was linked against is corrupt, improperly built, 
or misconfigured. This error can also be caused by malfunctioning hardware. 
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed, 
something is definitely wrong and this may fail.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4905183 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0 
Attempting backtrace. You can use the following information to find out 
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
130424 19:32:33 mysqld_safe Number of processes running now: 0
130424 19:32:33 mysqld_safe mysqld restarted 
130424 19:32:42 [Note] Plugin 'FEDERATED' is disabled. 
130424 19:32:42 InnoDB: The InnoDB memory heap is disabled 
130424 19:32:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130424 19:32:42 InnoDB: Compressed tables use zlib 1.2.3
130424 19:32:42 InnoDB: Using Linux native AIO
130424 19:32:42 InnoDB: Initializing buffer pool, size = 10.0G
130424 19:32:44 InnoDB: Completed initialization of buffer pool
130424 19:32:44 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 1528713295424 
130424 19:32:44  InnoDB: Database was not shut down normally!

How to repeat:
Run mysql.

Suggested fix:
Don't crash?
[24 Apr 2013 20:56] MySQL Verification Team
Are you check and try the below instruction of the log:

It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4905183 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

[24 Apr 2013 21:16] Greg Hazel
I have 128GB of memory. That amount is totally reasonable.
[24 Apr 2013 23:12] Valeriy Kravchuk
As you use Percona Server, it makes sense to report this bug at https://bugs.launchpad.net/percona-server. Make sure you attach the entire error log (compressed if it's big) or at least specify the exact version used (5.5.30-30.2).
[29 Apr 2013 10:06] MySQL Verification Team
Server was intentionally killed by innodb because innodb determined it was hanging.  Not enough information here to guess why. We'd need full error log at least; but report that at Percona bug database is better idea for now.
[13 Dec 2014 3:35] Yogesh Kore
I have faced pretty same problem here. Attaching error log file herewith if that helps to understand more and anyone can give fix or information on it.
[13 Dec 2014 3:36] Yogesh Kore
Error log file for bug here

Attachment: mysql.err (application/octet-stream, text), 666.07 KiB.