InnoDB: Assertion failure in thread 139704789141248 in file sync0sync.cc line 377 mutex_get_lock_word(mutex) == 0 Some pointers may be invalid and cause the dump to abort.

[skipper]

2016-08-22 18:05:59 7f0f8e548700 InnoDB: Assertion failure in thread 139704789141248 in file sync0sync.cc line 377
InnoDB: Failing assertion: mutex_get_lock_word(mutex) == 0
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
10:05:59 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/

key_buffer_size=67108864
read_buffer_size=131072
max_used_connections=854
max_threads=50002
thread_count=277
connection_count=277
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 20003428 K bytes of memory
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.
160822 18:06:00 mysqld_safe Number of processes running now: 0
160822 18:06:00 mysqld_safe mysqld restarted
2016-08-22 18:06:03 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-08-22 18:06:03 144416 [Note] Plugin 'FEDERATED' is disabled.
2016-08-22 18:06:03 144416 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-08-22 18:06:03 144416 [Note] InnoDB: The InnoDB memory heap is disabled
2016-08-22 18:06:03 144416 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-08-22 18:06:03 144416 [Note] InnoDB: Memory barrier is not used
2016-08-22 18:06:03 144416 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-08-22 18:06:03 144416 [Note] InnoDB: Using Linux native AIO
2016-08-22 18:06:03 144416 [Note] InnoDB: Using CPU crc32 instructions
2016-08-22 18:06:03 144416 [Note] InnoDB: Initializing buffer pool, size = 80.0G
2016-08-22 18:06:06 144416 [Note] InnoDB: Completed initialization of buffer pool
2016-08-22 18:06:07 144416 [Note] InnoDB: Highest supported file format is Barracuda.
2016-08-22 18:06:07 144416 [Note] InnoDB: Log scan progressed past the checkpoint lsn 202220831352
2016-08-22 18:06:07 144416 [Note] InnoDB: Database was not shutdown normally!
2016-08-22 18:06:07 144416 [Note] InnoDB: Starting crash recovery.
2016-08-22 18:06:07 144416 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-08-22 18:06:08 144416 [Note] InnoDB: Restoring possible half-written data pages
2016-08-22 18:06:08 144416 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 202220865928
InnoDB: 39 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 73 row operations to undo
InnoDB: Trx id counter is 413420032
2016-08-22 18:06:09 144416 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 967850935, file name mysql8-bin.000173
2016-08-22 18:06:10 144416 [Note] InnoDB: 128 rollback segment(s) are active.
InnoDB: Starting in background the rollback of uncommitted transactions
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413419561, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Waiting for purge to start
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413419561 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413419556, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413419556 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413419552, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413419552 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413419520, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413419520 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413419514, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413419514 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413419385, 3 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413419385 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413419350, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413419350 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413419346, 1 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413419346 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413419344, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413419344 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413419343, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413419343 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413419165, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413419165 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413419150, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413419150 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413419149, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413419149 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413418849, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413418849 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413418817, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413418817 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413418811, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413418811 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413418777, 2 rows to undo
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413418753, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413418753 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413418242, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413418242 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413418228, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413418228 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413418199, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413418199 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413418198, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413418198 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413418190, 1 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413418190 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413418187, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413418187 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413418179, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413418179 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413418126, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413418126 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413418096, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413418096 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413417845, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413417845 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413417843, 1 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413417843 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413417825, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413417825 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413417824, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413417824 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413417823, 1 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413417823 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413417785, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413417785 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413417713, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413417713 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413417709, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413417709 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413416936, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413416936 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413416822, 2 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413416822 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413415316, 1 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413415316 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rolling back trx with id 413415282, 1 rows to undo
2016-08-22 18:06:10 144416 [Note] InnoDB: Rollback of trx with id 413415282 completed
2016-08-22 18:06:10 7f2d4379a700 InnoDB: Rollback of non-prepared transactions completed
2016-08-22 18:06:10 144416 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.23-72.1 started; log sequence number 202220865928
2016-08-22 18:06:10 7f2d91096700 InnoDB: Loading buffer pool(s) from /opt/mysql/data/ib_buffer_pool
2016-08-22 18:06:10 144416 [Note] Recovering after a crash using mysql8-bin
2016-08-22 18:06:10 7f2d91096700 InnoDB: Buffer pool(s) load completed at 160822 18:06:10
2016-08-22 18:06:14 144416 [Note] Starting crash recovery...
2016-08-22 18:06:14 144416 [Note] Crash recovery finished.
2016-08-22 18:06:14 144416 [Note] RSA private key file not found: /opt/mysql/data//private_key.pem. Some authentication plugins will not work.
2016-08-22 18:06:14 144416 [Note] RSA public key file not found: /opt/mysql/data//public_key.pem. Some authentication plugins will not work.
2016-08-22 18:06:14 144416 [Note] Server hostname (bind-address): '*'; port: 3331
2016-08-22 18:06:14 144416 [Note] IPv6 is available.
2016-08-22 18:06:14 144416 [Note] - '::' resolves to '::';
2016-08-22 18:06:14 144416 [Note] Server socket created on IP: '::'.
2016-08-22 18:06:14 144416 [Warning] 'user' entry 'root@mysql8' ignored in --skip-name-resolve mode.
2016-08-22 18:06:14 144416 [Warning] 'user' entry '@mysql8' ignored in --skip-name-resolve mode.
2016-08-22 18:06:14 144416 [Warning] 'proxies_priv' entry '@ root@mysql8' ignored in --skip-name-resolve mode.
2016-08-22 18:06:14 144416 [Note] Event Scheduler: Loaded 0 events
2016-08-22 18:06:14 144416 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.23-72.1-log' socket: '/opt/mysql/mysql.sock' port: 3331 Percona Server (GPL), Release 72.1, Revision 0503478

[Shahriyar Rzayev (rzayev-sehriyar)]

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