Bug #76282 mysqld crashes on a Debian 7 system
Submitted: 12 Mar 2015 9:37 Modified: 12 Mar 2015 13:40
Reporter: Victor Porton Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S1 (Critical)
Version:5.5.41-0+wheezy1 OS:Linux (debian-linux-gnu on x86_64)
Assigned to: CPU Architecture:Any

[12 Mar 2015 9:37] Victor Porton
It happened after a system update, probably after installing libssh2-1 1.4.2-1.1+deb7u1.

mysqld  Ver 5.5.41-0+wheezy1 for debian-linux-gnu on x86_64

# mysqld
150312  9:27:45 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
150312  9:27:45 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150312  9:27:45 [Note] Plugin 'FEDERATED' is disabled.
150312  9:27:45 InnoDB: The InnoDB memory heap is disabled
150312  9:27:45 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150312  9:27:45 InnoDB: Compressed tables use zlib 1.2.7
150312  9:27:45 InnoDB: Using Linux native AIO
150312  9:27:45 InnoDB: Initializing buffer pool, size = 128.0M
150312  9:27:45 InnoDB: Completed initialization of buffer pool
150312  9:27:45 InnoDB: highest supported file format is Barracuda.
150312  9:27:45  InnoDB: Waiting for the background threads to start
150312  9:27:46 InnoDB: 5.5.41 started; log sequence number 58306419610
150312  9:27:46 [Note] Server hostname (bind-address): ''; port: 3306
150312  9:27:46 [Note]   - '' resolves to '';
150312  9:27:46 [Note] Server socket created on IP: ''.
150312  9:27:46 [Note] Event Scheduler: Loaded 0 events
150312  9:27:46 [Note] mysqld: ready for connections.
Version: '5.5.41-0+wheezy1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)
150312  9:27:46  InnoDB: Assertion failure in thread 140397129611008 in file trx0purge.c line 840
InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
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.
09:27:46 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.

It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346700 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 0x30000
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

How to repeat:
# mysqld
[12 Mar 2015 9:43] Victor Porton
The bug persists with mysqld Ver 5.5.42-1 for debian-linux-gnu on x86_64
[12 Mar 2015 13:40] MySQL Verification Team
same as https://bugs.mysql.com/bug.php?id=61516