system crashes randomly and frequently
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.6 |
Incomplete
|
Undecided
|
Anna |
Bug Description
Recently I posted a new bug report about my system just randomly crashing usually about once per day. I was then told the bug causing this was already identified and reported here: https:/
If you read about that bug, it says that it only happens if you have binlog turned OFF (which I had). So I turned binlog on, but yet my system is still crashing, perhaps even a little more frequently now than before I turned on binlog. Here is the output in error.log:
17:52:17 UTC - mysqld got signal 11 ;
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 XtraDB Cluster better by reporting any
bugs at https:/
key_buffer_
read_buffer_
max_used_
max_threads=402
thread_count=53
connection_count=53
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f6bfe3ce000
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 = 7f6be91f3dc0 thread_stack 0x30000
/usr/sbin/
/usr/sbin/
/lib/x86_
/lib/x86_
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib/x86_
/lib/x86_
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 143
Status: NOT_KILLED
You may download the Percona XtraDB Cluster operations manual by visiting
http://
in the manual which will help you identify the cause of the crash.
140903 11:52:17 mysqld_safe Number of processes running now: 0
140903 11:52:17 mysqld_safe mysqld restarted
140903 11:52:17 mysqld_safe Skipping wsrep-recover for empty datadir: /var/lib/mysql
140903 11:52:17 mysqld_safe Assigning 00000000-
2014-09-03 11:52:17 0 [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.
2014-09-03 11:52:17 0 [Note] WSREP: wsrep_start_
2014-09-03 11:52:17 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_
2014-09-03 11:52:17 15659 [Warning] Using unique option prefix myisam-recover instead of myisam-
2014-09-03 11:52:17 15659 [Note] Plugin 'FEDERATED' is disabled.
2014-09-03 11:52:17 15659 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-09-03 11:52:17 15659 [Note] InnoDB: The InnoDB memory heap is disabled
2014-09-03 11:52:17 15659 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-09-03 11:52:17 15659 [Note] InnoDB: Compressed tables use zlib 1.2.8
2014-09-03 11:52:17 15659 [Note] InnoDB: Using Linux native AIO
2014-09-03 11:52:17 15659 [Note] InnoDB: Using CPU crc32 instructions
2014-09-03 11:52:17 15659 [Note] InnoDB: Initializing buffer pool, size = 40.0G
2014-09-03 11:52:19 15659 [Note] InnoDB: Completed initialization of buffer pool
2014-09-03 11:52:19 15659 [Note] InnoDB: Highest supported file format is Barracuda.
2014-09-03 11:52:19 15659 [Note] InnoDB: Log scan progressed past the checkpoint lsn 2357398215693
2014-09-03 11:52:19 15659 [Note] InnoDB: Database was not shutdown normally!
2014-09-03 11:52:19 15659 [Note] InnoDB: Starting crash recovery.
2014-09-03 11:52:19 15659 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-09-03 11:52:19 15659 [Note] InnoDB: Restoring possible half-written data pages
2014-09-03 11:52:19 15659 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 2357403458560
InnoDB: Doing recovery: scanned up to log sequence number 2357408701440
InnoDB: Doing recovery: scanned up to log sequence number 2357413944320
InnoDB: Doing recovery: scanned up to log sequence number 2357419187200
InnoDB: Doing recovery: scanned up to log sequence number 2357424430080
InnoDB: Doing recovery: scanned up to log sequence number 2357429672960
InnoDB: Doing recovery: scanned up to log sequence number 2357434915840
InnoDB: Doing recovery: scanned up to log sequence number 2357440158720
InnoDB: Doing recovery: scanned up to log sequence number 2357445401600
InnoDB: Doing recovery: scanned up to log sequence number 2357450644480
InnoDB: Doing recovery: scanned up to log sequence number 2357455887360
InnoDB: Doing recovery: scanned up to log sequence number 2357461130240
InnoDB: Doing recovery: scanned up to log sequence number 2357466373120
InnoDB: Doing recovery: scanned up to log sequence number 2357471616000
InnoDB: Doing recovery: scanned up to log sequence number 2357476858880
InnoDB: Doing recovery: scanned up to log sequence number 2357482101760
InnoDB: Doing recovery: scanned up to log sequence number 2357487344640
InnoDB: Doing recovery: scanned up to log sequence number 2357492587520
InnoDB: Doing recovery: scanned up to log sequence number 2357497830400
InnoDB: Doing recovery: scanned up to log sequence number 2357503073280
InnoDB: Doing recovery: scanned up to log sequence number 2357508316160
InnoDB: Doing recovery: scanned up to log sequence number 2357513559040
InnoDB: Doing recovery: scanned up to log sequence number 2357518801920
InnoDB: Doing recovery: scanned up to log sequence number 2357524044800
InnoDB: Doing recovery: scanned up to log sequence number 2357529287680
InnoDB: Doing recovery: scanned up to log sequence number 2357534530560
InnoDB: Doing recovery: scanned up to log sequence number 2357539773440
InnoDB: Doing recovery: scanned up to log sequence number 2357545016320
InnoDB: Doing recovery: scanned up to log sequence number 2357550259200
InnoDB: Doing recovery: scanned up to log sequence number 2357555502080
InnoDB: Doing recovery: scanned up to log sequence number 2357560744960
InnoDB: Doing recovery: scanned up to log sequence number 2357565987840
InnoDB: Doing recovery: scanned up to log sequence number 2357571230720
InnoDB: Doing recovery: scanned up to log sequence number 2357576473600
InnoDB: Doing recovery: scanned up to log sequence number 2357581716480
InnoDB: Doing recovery: scanned up to log sequence number 2357586959360
InnoDB: Doing recovery: scanned up to log sequence number 2357592202240
InnoDB: Doing recovery: scanned up to log sequence number 2357597445120
InnoDB: Doing recovery: scanned up to log sequence number 2357602688000
InnoDB: Doing recovery: scanned up to log sequence number 2357607930880
InnoDB: Doing recovery: scanned up to log sequence number 2357613173760
InnoDB: Doing recovery: scanned up to log sequence number 2357614493851
InnoDB: Transaction 4124481611 was in the XA prepared state.
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 0 row operations to undo
InnoDB: Trx id counter is 4124482048
2014-09-03 11:52:21 15659 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 378198424, file name mysql-bin.000496
2014-09-03 11:52:24 15659 [Note] InnoDB: 128 rollback segment(s) are active.
InnoDB: Starting in background the rollback of uncommitted transactions
2014-09-03 11:52:24 7ff38d7ff700 InnoDB: Rollback of non-prepared transactions completed
2014-09-03 11:52:29 15659 [Note] InnoDB: Waiting for purge to start
2014-09-03 11:52:29 15659 [Note] InnoDB: Percona XtraDB (http://
2014-09-03 11:52:29 15659 [Note] Recovering after a crash using /var/log/
2014-09-03 11:52:29 15659 [Note] WSREP: Binlog recovery, found wsrep position 00000000-
2014-09-03 11:52:30 15659 [Note] WSREP: Binlog recovery scan stopped at Xid event 2065850
2014-09-03 11:52:30 15659 [Note] Starting crash recovery...
2014-09-03 11:52:30 7ffea39117c0 InnoDB: Starting recovery for XA transactions...
2014-09-03 11:52:30 7ffea39117c0 InnoDB: Transaction 4124481611 in prepared state after recovery
2014-09-03 11:52:30 7ffea39117c0 InnoDB: Transaction contains changes to 1 rows
2014-09-03 11:52:30 7ffea39117c0 InnoDB: 1 transactions in prepared state after recovery
2014-09-03 11:52:30 15659 [Note] Found 1 prepared transaction(s) in InnoDB
2014-09-03 11:52:30 15659 [Note] Crash recovery finished.
2014-09-03 11:52:30 15659 [Note] RSA private key file not found: /var/lib/
2014-09-03 11:52:30 15659 [Note] RSA public key file not found: /var/lib/
2014-09-03 11:52:30 15659 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
2014-09-03 11:52:30 15659 [Note] - '0.0.0.0' resolves to '0.0.0.0';
2014-09-03 11:52:30 15659 [Note] Server socket created on IP: '0.0.0.0'.
2014-09-03 11:52:30 15659 [Note] Event Scheduler: Loaded 0 events
2014-09-03 11:52:30 15659 [Note] WSREP: Read nil XID from storage engines, skipping position init
2014-09-03 11:52:30 15659 [Note] WSREP: wsrep_load(): loading provider library 'none'
2014-09-03 11:52:30 15659 [Note] [Debug] WSREP: dummy_init
2014-09-03 11:52:30 15659 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.19-
Hi,
We update Percona XtraDB Cluster from "5.6.15" to "5.6.19" and after that to "5.6.20". In both cases we have same issue.
My log file in attachment